Good Afternoon, and apologies in advance if this has been covered a hundred
times before.
I'm doing some development work, in Access 03 and distributing the prog with
the runtime version.
Trouble is, I have some clients who are using Office XP, and they are
getting the "incompatible database format" issue when trying to use the same
MDE I'm shipping out with the 2003 runtime.
The only solution I know of is to save it as a 2000 file format, bring it
into a machine running office XP, and make a new MDE from there. While it
works, it's not real efficient and also effectively doubles the number of
versions that are out there.
Soooo ... is there any way to tell Access 2003 that you want to make a MDE
for Access XP, or better yet, have that be the default, since 2003 should
have no issues running an XP front end???
Thanks for any thoughts:
Kevin
Douglas J. Steele - 16 Dec 2005 20:06 GMT
Unfortunately, there's no way to do what you want. Each version of Access
can only create MDE files in its own format, even if they're capable of
working with other file formats.

Signature
Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no e-mails, please!)
> Good Afternoon, and apologies in advance if this has been covered a
> hundred times before.
[quoted text clipped - 18 lines]
>
> Kevin
MOHAMED - 16 Dec 2005 21:36 GMT
> Good Afternoon, and apologies in advance if this has been covered a hundred
> times before.
[quoted text clipped - 18 lines]
>
> Kevin
davidp - 21 Dec 2005 17:21 GMT
Kevin, tis is exactly what I am doing. I've got hundreds of users using
office 2k, xp and 2003.
In Access 2003, set the default to office 2k and develop in that
enviornment.
I have another machine that has 2k on it, on that machine I'll compile it
and fix any compatability issues and create my MDE's.
Then dstribute the MDE. I haven't had any issues in the past 3 years.
> Good Afternoon, and apologies in advance if this has been covered a hundred
> times before.
[quoted text clipped - 18 lines]
>
> Kevin