I have a cust who has upgrade MB Fosters ODBC driver from 55.01 to 56.09
(SQLKX53).

They have a test program that uses the SQLCONNECT call while they use
Centura software which uses the SQLDRIVERCONNECT call.  The parameters
to this call include the DSN, UID and password such as:

DSN=PMS;UID=#mpeix/central:PMSDBE,,an#WSC783,MGR/.DUMMY/,DBE/

The previously version of the driver would allow a bogus uid to be
entered and it would then get the correct uid from the registry, using
the value of the dsn. In Centura you cannot pass a blank uid as it will
then insert 'sysadm' as the default and try and connect using that
string which will fail.

He was eventually able to set the uid to the correct value on Centura,
but when it passed it to a lower layer it had the error 'more than two
slashes in connect string', due to the make-up of the uid.

An SR was raised to stop having to put the value of the uid in an 'ini'
file (16bit) or the registry so that passwords could not be found which
at the same time has reduced the functionality of the driver.

Has anyone else come across this problem, and has found a solution.

Richard Bayly