.mde unrecognizable database format

[Cloonalt]

We have a number of .mde Access databases working on PCs with MS Access not installed. However, we just hit a situation where we get an "unrecognizable database format" error when we try to open an Access .mde.

Same .mde works on some computers, not on other. Even the icon is changed on the PCs where the .mde doesn't work.

Any ideas?

Thanks.

 

[PHV]

The .mde should be compiled with the same version of access as the runtime.

Hope This Helps, PH.
Want to get great answers to your Tek-Tips questions? Have a look at FAQ219-2884 or FAQ181-2886

 

[Cloonalt]

Not sure what you mean, PHV. We have one .mde on a network drive that was compiled with Access 2000.

It opens fine on some user's computers and not others. Seems to be specific to a user or user's computer.

Thanks for your response.

 

[PHV]

Each user's computer should have either full access 2000 or RT access 2000, i.e. a .mde compiled with ac2k should be open with ac2k.

Hope This Helps, PH.
Want to get great answers to your Tek-Tips questions? Have a look at FAQ219-2884 or FAQ181-2886

 

[Cloonalt]

Most of our users don't have full Access 2000 installed. So I guess they have Access 2000 run time installed? Is that part of the Office install, do you know?

Thanks for your response.

 

[PHV]

The ac2k RT is not part of the Office install.
You must have one Office developper edition in order to generate an installable package.

Hope This Helps, PH.
Want to get great answers to your Tek-Tips questions? Have a look at FAQ219-2884 or FAQ181-2886

 

[Cloonalt]

I have full Access 2000 installed on my computer. I created an .mde which I put on a network drive. We have users using that .mde who don't have Access 2000 installed on their computer.

Now new users without Access installed on their computers were given rights to that network drive to use the .mde. They get an error "unrecognizable ...."

Do the users getting the error need something additional installed on their computers?

Thanks.

 

[Cloonalt]

Seems like the problem was solved by installing Office Service Pack 2 on the problem machnes.