I am working on a project and developing the application using Access 2003.

The end user will be using Access 2000. Are there any problems I should expect?

Thank you,

Hi,

I haven't done that in a while but the only thing I can remember is that if you use ADO in your code, you may have to convert them to DAO (or was it the other way around?).

Hope that helps...

I think you just need to make sure the database is in 2000 format. Both versions have ADO and DAO available, so I don't think that will be an issue.

Guys,

Thanks for the advise. I will probably proceed with the development.

Dave

This comes around from time to time.
The crux is that compatibility is very good - but you need to be aware of the functionality that Access itself supports in 2003 which 2000 doesn't (the file formats are very acceptable).

ADO won't be much of an issue (there are cases where 2003 works better with it - but I'd find it unlikely you'll be venturing into them).
The core functionality is roughly consistent.
(FWIW you can use ADO in Access 97 if you so choose! You just can't avail yourself of the 2000+ convenience of the CurrentProject.Connection object and such like).

As I said this comes around from time to time - I'll point to at least one such previous example.

Edit: Following that link - I'm fairly certain that 2002 actually introduced the ExportXML and ImportXML methods. Just thought I'd post that correction.
(Sorry - it's too much effort to actually boot up a version of 2002 to verify ;-)

Cheers.

Edited by: LPurvis on Fri Mar 6 20:15:46 EST 2009.