Visual basic 3.0 accessing Access 2.0 databases
Quote:
>Hello,
>I've read in the Microsoft knowledge base that you can install a
>compatibility layer to use Access 2.0 database from Visual Basic 3.0.
>Two questions about this:
>- if you distribute such an application, it appears that the VBDB300.DLL
>file on the target PC will be replaced by a new version, included in this
>compatibility layer software. If there are older 3.0 applications on this
>PC using Access 1.1 databases, will they still work ?
The other VB/Access 1.1 applications will still work OK. BUT, if the other VB
applications 'compacts' its 1.1 database, it will be automatically upgraded to
Access 2.0, and there's no way to control it. There's a switch mentioned in
the doc somewherethat is SUPPOSED to control this, but it doesn't work. This
is confirmed in another KB article, the number of which escapes me at the
moment.
This may not be a big deal, but if the user is still using Access 1.1 to get
to the VB app's 1.1 databases, i.e.they don't have Access 2.0, then they are
dead in the water. It may take them a while, but they will eventually figure
out it was YOUR app that messed things up for them. For this reason, we don't
send out the compatibility layer with our VB 3 applications. If the user
already has it, fine, no problem. If they want it, we provide it as a separate
installation.Your installation program needs to be smart enough not to replace
the newer VBDB300.
Quote:
>- Microsoft states that you can find this compatibility layer in the
>Access Developer's Toolkit. Does anybody know where you can get the
>necessary files without purchasing this toolkit.
I think it is called comlyr.exe on their FTP site. It does NOT include the
MSAJT200.DLL Jet 2 engine. Microsoft assumes you got that with Access 2.0.
Quote:
>Thanks in advance for any bright ideas.
>Luc Jacobs
