We can't guarantee anything. However I work in A2000 format MDBs in A2003. And then
create the MDE in A2000 and it works fine.
However I would think that it would work. You might need to do a decompile in A2003
to clean things up occasionaly. You might have to do a Save As to save the MDB in
A2000 format to really clean things up but there aren't any significant features in
A2002/2003. Hmm, other than the printer object which I've never used.
Worst case scenario is that you might have to do a SaveAsText for all your forms,
reports and modules and import them again.
Corrupt Objects within a Corrupt Microsoft Access MDB
The little documented SaveAsText and LoadFromText may help if an object is corrupted
or otherwise behaving weirdly.
At the debug/immediate window type:
You can load the file into a new MDB.
Sample code at http://www.yqcomputer.com/
in an MDB.
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
Tony's Microsoft Access Blog - http://www.yqcomputer.com/