Access 2000 & 2003 on network

[tmb]

The data format for Access 2000 and 2003 seem to be different.

I have a network on which some clients have Office/Access 2000 and some have
Office/Access 2003.

What is the solution for sharing Access databases between these two groups?

There is no way to afford updating all computers to Office/Access 2003 at
this time.

This is a real problem.

How have you guys handled this? What are your 'real world' suggestions.

thanks

 

[Sylvain Lafontaine]

Divide the database into two files: the FrontEnd and the Backend. (There is
a wizard for doing this). Then give each user his own copy of the frontend.

You will find a lot of messages about this topic in the previous posts.

S. L.

 

[Tony D'Ambra]

Both Access2000 and Access 2003 support the Access2000 file format, so
deploy the app as an Access2000 database(s).

Tony D'Ambra
Web Site: aadconsulting.com
Web Blog: accessextra.net

 

[Todd Shillam]

I would have to agree with Tony's remarks--this simplifies version control.
By creating the 'front-end' application in the 2000 format, you will not
have to spend twice the effort that is involved in maintaining two separate
applications for each platform, the 2000 and 2003 versions of Microsoft
Access.

I do know the 'references' in any modules may use different files--this may
cause compatibility issues. Otherwise, should work just fine.

I would split the program into two parts, the 'back-end' (your tables) and a
'front-end' (the computer application). Then I would use UNC or drive
mapping to link the computer application to your back-end tables.
Personally, I prefer drive mapping.

Best regards,

Todd

 

[Andrew Baldozier]

hiyall