I am trying to create a DataSource using a proprietary JDBC driver. The problem 
I am encountering is that this driver (or to be more exact theserver side of the 
driver) is rejecting the request to show the tabledefinition because the request 
is malformed.It seems it doesn't like an attribute without a value. Here is the 
trace I get on the server side.  
The attribute EnableSQL92Check doesn't have a value regardless if it is checked 
or not. Note that I am not sure if this is what make it choke. This is a 
proprietary product and like with all of them it takes forever to get a straight 
answer. I am using OpenOffice.org1.1rc4 on Linux with Java 1.4.2-01. I tried with 
Java 1.3.1-09 and OpenOffice.org.1.0.1 just do be sure. 
 
>SQLDriverConnect(0x081e51bc, 
0x0000,"EnableSQL92Check=;UID=root;DSN=CRS;PWD=;AutoIncrementCreation=;",-3, 
0xbfffd348, 256, 0xbfffce54, 0)        >DrmBeginSession("root", "CRS")        
<DrmBeginSession returned 0 (SesID=1)        >DrmSetSessionOption(1, 
SetIniValue, "Catalog,/usr/lib/relativity/RelRM5.00/crs/rm/crs.rcg")        
<DrmSetSessionOption returned 0.        >DrmSetSessionOption(1, SetIniValue, 
"FileMgr,RM")        <DrmSetSessionOption returned 0.        
>DrmOpenDatabase(1, "CRS", DRM_bitDbShared)        >FMInit(081F02E4, 
081F02C8 (Task=0000170C), pErrorCode, pInfoCode)        <FMInit returned 1.        
<DrmOpenDatabase returned 0 (1)        >DrmCloseTable(1, 1)        
<DrmCloseTable returned 0.        >DrmSetTransact(1, DRM_AUTO_COMMIT)        
<DrmSetTransact returned 0.        <SQLDriverConnect returned 1.        
>SQLError(0x081e36dc, 0x081e51bc, 0x00000000, 0x081e4754, 0x081e475c, 
0x081e4760, 511, 0x00000000)          SqlState: "01S00"          NativeError: 0          
ErrorMsg: [Liant][Relativity RM Server]Invalid connection string attribute.        
<SQLError returned 0. 
 
This was copied directly from an email I wrote to the dba.openoffice.org list.  
Frank Schönheit <fs@openoffice.org> then responded 
 
this "EnableSQL92Check=" here in the connection string looks like the root 
cause: It's a parameter used internally in OOo, and it should never be passed to 
the system JDBC driver, but (at most) be evaluated by ourSDBC driver only.