
VB6/Access 97 app on computer running Access 2000
If your VB just needs to see/change tables in the database, it should
not matter that the version of your .mdb may be an older version of
Access that the person using your program has. However, if you
actually need to have your VB program open Access (to run a macro,
show a report, run a query..etc) then on the user's computer, it will
attempt to open an Access 97 database using Access 2000. A prompt on
their display would ask them if they would want to convert the
database to a 2000 version. If they elected not to, it might ask this
every time. If they did convert it, yourself (the developer) would not
be able to go back into the database if you needed to check something
for them.
-Roger
Quote:
> I've written an application using VB6 connecting to an Access 97
> database. I've used the Package & Deployment Wizard to create an
> installation CD. Most of the users are running Access 97 (or nothing).
> However some users at a different site are apparently running Access
> 2000.
> My question is, if I give the installation CD to the Access 2000
> users, will they be able to install and run my program even though
> they have Access 2000 installed? Will the VB6 program still work with
> the Access 97 database, alongside a full installation of Access 2000?
> What sort of issues do I face with this? I don't want to break their
> Access 2000 installation, but I also would prefer not to build a
> separate Access 2000 version, especially as I don't even have a copy
> of Access 2000.
> Any advice would be greatly appreciated.
> Stuart Allen