We had an external developer create a MDE wich should be connecting to a back
end SQL database.

It has been some time since I actually tried to use this MDE. We were
advised to makes sure clients had Access 2003 with SP2 installed.

I actually tried to open the MDE file and got a message:

"You do not have the correct version. Please get the latest version"

We currently currently have not yet entered any data, do I also got a clean
version of the MDE and also restored the SQL database from the original that
was set up by the consultant.

Any suggestions as to what could have caused this issue would be greatly
apppreciated.

regards

The error message suggests that the .MDE was created using one version of
Access, and the version you have does not match.

You'll probably need to confirm both -- which version it was created in and
which you have. They'll have to match.

Regards

Jeff Boyce
Microsoft Office/Access MVP


"PolarBear" <(E-Mail Removed)> wrote in message
news:E662F589-9C68-48C6-9D0F-(E-Mail Removed)...
> We had an external developer create a MDE wich should be connecting to a
> back
> end SQL database.
>
> It has been some time since I actually tried to use this MDE. We were
> advised to makes sure clients had Access 2003 with SP2 installed.
>
> I actually tried to open the MDE file and got a message:
>
> "You do not have the correct version. Please get the latest version"
>
> We currently currently have not yet entered any data, do I also got a
> clean
> version of the MDE and also restored the SQL database from the original
> that
> was set up by the consultant.
>
> Any suggestions as to what could have caused this issue would be greatly
> apppreciated.
>
> regards
>

> We were
> advised to makes sure clients had Access 2003 with SP2 installed.
>
> I actually tried to open the MDE file and got a message:
>
> "You do not have the correct version. Please get the latest version"

This is developer-defined error message, not a built-in Access message.
Therefore, the database file opened and either VBA code or a macro ran in
the start up to produce this message for you, indicating that you aren't
using an earlier version of Access than the database file format. Most
likely, this is Access 2003 database format, but it could also be Access
2000 or 2002 database format. To find out, hold the <SHIFT> key down and
open the database, keeping the key pressed until the database is completely
open to bypass the startup options. If the Database Window is displayed,
then its title bar will display which database format, such as:

DBName: Database (Access 2003 file format)

That doesn't matter nearly as much as what the VBA code or macro is
requiring: the correct version of Access (especially since you can't change
or upgrade the database file format of an MDE database file). Select the
Help -> About Microsoft Office Access menu to determine the version of
Access and service pack level you are using, which will be listed at the top
of the dialog window. Either yours isn't Microsoft Office Access 2003
(build number) SP-2, or it doesn't have the intended build number due to
more recent Office updates.

If it's a macro being run, then you can probably remove that criteria or
change it, but if it's VBA code, then you won't be able to make a change to
that since it's an MDE database file. You'll need to get the original MDB
database file that the MDE database file was created from and make the
change in the MDB database file, then regenerate an MDE database file.

If it's VBA code generating the error message and not a macro, then the bad
news is that even if you install both service packs so that you can use the
database file, when Microsoft Office 2003 SP-3 comes out your database file
will likely again be worthless to you until someone changes the code in the
MDB database file to allow for SP-3 and regenerates another MDE database
file. And likely worthless yet again when you upgrade to Access 2007 or
future versions.

HTH.
Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips and tutorials.
Blogs: www.DataDevilDog.BlogSpot.com, www.DatabaseTips.BlogSpot.com
http://www.Access.QBuilt.com/html/ex...ributors2.html for contact
info.

"Jeff Boyce" <(E-Mail Removed)> wrote:

>The error message suggests that the .MDE was created using one version of
>Access, and the version you have does not match.
>
>You'll probably need to confirm both -- which version it was created in and
>which you have. They'll have to match.

Versions of Access newer than A2000 can run MDE's created in older
versions of Access back to A2000. That is A2007 can run an A2002 MDE.

Tony
--
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
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/

Outstanding!

So the original poster must be trying to open a newer version MDE with an
older version of Access?

Jeff

"Tony Toews [MVP]" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> "Jeff Boyce" <(E-Mail Removed)> wrote:
>
>>The error message suggests that the .MDE was created using one version of
>>Access, and the version you have does not match.
>>
>>You'll probably need to confirm both -- which version it was created in
>>and
>>which you have. They'll have to match.
>
> Versions of Access newer than A2000 can run MDE's created in older
> versions of Access back to A2000. That is A2007 can run an A2002 MDE.
>
> Tony
> --
> 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
> http://www.granite.ab.ca/accsmstr.htm
> Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/

Hi, Jeff.

> So the original poster must be trying to open a newer version MDE with an
> older version of Access?

No. He'd get an "Invalid database format" message and the file would not be
opened. Instead, the file is actually opening, running either VBA code or a
macro (which runs a VBA procedure) on start up that checks the Access
version and service pack (and possibly the build number). If it isn't
Access 2003 SP-2, then it gives the error message and quits. Not very
flexible.

HTH.
Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips and tutorials.
Blogs: www.DataDevilDog.BlogSpot.com, www.DatabaseTips.BlogSpot.com
http://www.Access.QBuilt.com/html/ex...ributors2.html for contact
info.

Thanks, Gunny.

That makes sense, in a painful sort of way...<g>

Jeff B.

"'69 Camaro" <(E-Mail Removed)_SPAM> wrote in
message news:(E-Mail Removed)...
> Hi, Jeff.
>
>> So the original poster must be trying to open a newer version MDE with an
>> older version of Access?
>
> No. He'd get an "Invalid database format" message and the file would not
> be opened. Instead, the file is actually opening, running either VBA code
> or a macro (which runs a VBA procedure) on start up that checks the Access
> version and service pack (and possibly the build number). If it isn't
> Access 2003 SP-2, then it gives the error message and quits. Not very
> flexible.
>
> HTH.
> Gunny
>
> See http://www.QBuilt.com for all your database needs.
> See http://www.Access.QBuilt.com for Microsoft Access tips and tutorials.
> Blogs: www.DataDevilDog.BlogSpot.com, www.DatabaseTips.BlogSpot.com
> http://www.Access.QBuilt.com/html/ex...ributors2.html for contact
> info.
>
>

"Jeff Boyce" <(E-Mail Removed)> wrote:

>So the original poster must be trying to open a newer version MDE with an
>older version of Access?

I'm with Gunny. That sure looks like a VBA message to me.

Tony
--
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
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/