Update an Access 2003 DB by using Access 2000

[Ragnar Midtskogen]

Hi,

Are there any possible problems using Access 2000 to update an Access 2003
application?
I have been asked to make some simple changes to an Access 2003 application
but I don't have 2003 on my machines.
I could install 2003, but if I don't have to I want to hold off until I
clean up the machines a bit.
I have made a few changes to the app, and so far so good. I just want to
make sure something doesn't break when the client gets the updated version.

Any comments would be appreciated.

 

[Allen Browne]

You should be fine.

Potential pitfalls:
1. If the mdb uses the A2002/03 file format, you will not be able to do
anything.

2. You may have problems if it uses new functionality that was not in A2000,
e.g. the Printer object or opening reports in dialog view.

3. References may break if it uses ActiveX controls (e.g. Microsoft
Calendar), or libraries for other Office applications (can avoid this by
late binding.)

4. Make sure you have the latest service pack for JET 4. Details:
http://support.microsoft.com/kb/239114
This ensures you are using the same engine as in Access 2003.

5. The compiled binary is different for each version of Access, so you might
want to decompile before switching versions. (This can solve weird errors
that seem meaningless.)

To decompile, enter something like this at the command prompt while Access
is not running. It is all one line, and include the quotes:
"c:\Program Files\Microsoft office\office\msaccess.exe" /decompile
"c:\MyPath\MyDatabase.mdb"
Then compact the database.

 

[Ragnar Midtskogen]

Thank you Allen,

Potential pitfalls:
1. If the mdb uses the A2002/03 file format, you will not be able to do
anything.

Well, that is clearly not the case, I can make changes without any
complaints.

2. You may have problems if it uses new functionality that was not in
A2000, e.g. the Printer object or opening reports in dialog view.

None that I am aware of, this is a very simple application.

3. References may break if it uses ActiveX controls (e.g. Microsoft
Calendar), or libraries for other Office applications (can avoid this by
late binding.)

It uses DAO 3.6 and ADO 2.1, and ADO is the default, for Access 2000 at
least

4. Make sure you have the latest service pack for JET 4. Details:
http://support.microsoft.com/kb/239114
This ensures you are using the same engine as in Access 2003.

I think I do, but I will check

5. The compiled binary is different for each version of Access, so you
might want to decompile before switching versions. (This can solve weird
errors that seem meaningless.)

To decompile, enter something like this at the command prompt while Access
is not running. It is all one line, and include the quotes:
"c:\Program Files\Microsoft office\office\msaccess.exe" /decompile
"c:\MyPath\MyDatabase.mdb"
Then compact the database.

Good idea, I will do that