Using Access 2000 files in 2003 and back again

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hi there,

The scenario is this:

The customer has Access 2000 on Win 2000, developer (me) has Access 2003 on
WinXP.

I'm able to open, debug, etc. the files in 2003 (I didn't convert, just
registered a dao dll (350 I think)). All seems well until I send the new
file back to the customer who gets "Can't find Project or Library".

I'm guessing that by working on the 2000 file in 2003 and saving it I have
performed some kind of implicit conversion to 2003 which can't be converted
back to 2000? - just a guess.

Any suggestions please.
Ta

Gary
 
Most likely, when you're editing the database, the References are getting
updated to Office 11 / ACCESS 11. Then your customer tries to use the
database but he needs Office 9 / ACCESS 9. He can fix this by resetting the
References to the correct ACCESS library when he gets the database back from
you.
 
We are in a similar situation here. This is our method for moving anything
with VBA code in it:
1. Form or Report is developed in 2003 using 2000 format
2. A temporary "transfer" mdb is created from 2003 using 2000 format
3. Open the transfer mdb and import the objects
4. Open each object in design mode.
5. Cut the code from the object's module and pasted it into a Wordpad file.
6. Set the Has Module property of the object to No and save the object
7. Using 2000, Import the codeless objects
8. Open each object in design mode.
9. Paste the code from the Wordpad file
10. Save the object

For standard modules, save them to a Wordpad file while in 2003
Then in 2000 create a new module as paste the code from the Wordpad file

This is, admittedly, tedious, but it avoids reference and corruption problems.
 
Back
Top