VB6 SP4 and Access 2000

[Jim]

The problem I have is getting a VB6 (SP4) application
that previously worked with Access 97 to work correctly
with Access 2000, (where the mdb tables were/are linked
to a Oracle backend via SQLNET). This may not be
relevant. I have converted the mdb file to 2000 using
both the old and new .mdw files. In both cases an error
occurs when using the VB
script "DBengine.createworkspace" where the username
and/or password do not seem to be recognised. Are there
compatibilitiy issues with this combination? Should I be
running a later Service Pack for VB6?

 

[david epsom dot com dot au]

Using DAO 3.6, you should be able to open and use
either the old (Jet 3.5) workgroup or the new (jet 4.0)
workgroup. With this workgroup, you should be able to
open the new (Jet 4.0) mdb. If this does not work, you
have probably made a mistake. I would expect a
different kind of error if there was an installation
problem with DAO 3.6

There are not any known compatibility issues, and the
relevant service pack just made it easier for developers
to choose dao 3.6 when using bound controls.

(david)