MDE Problem

M

Mike

Here's a weird one for the group. All of a sudden when I
compile and create a MDE file and transfer it to other
computers (10 of them) it crashes when it is opened on all
10 computers. If I open it on the machine I created it on
it opens fine.

Here's the kicker - if I create it on the other machines
and then move it onto my computer it opens fine.

Therefore, there is obviously a problem on my machine.
I'm running 97 SR2 with Jet 3.51 SP3. All the other
machines are running the same setup.

What files are used in creating a MDE? I figure that
maybe some of the DLLs are different on my machine.

Thanks
Mike
 
A

Allen Browne

For a list of the usual references for each version of Access, see:
http://allenbrowne.com/ser-38.html

Search your hard disk for msjet35.dll (typically in windows\system32) and
dao350.dll (typically in c:\program files\common files\microsoft
shared\dao ). There should be ONE copy of each only. If there are others,
remove them and re-register the libraray if necessary (as described in the
article.) Right-click these files in the Windows Explorer/My Computer, and
choose Properties. Look on the Version tab. Are the versions the same on the
computers where the code fails? Check the version of msaccess.exe as well.

Are the other systems running the same version of Windows? That can make a
difference if you are using a complete runtime installation, not simply to
coping an mde.
 
M

Mike

Allen,
Thanks for your reply. I searched for both files and I
only have one of each. I went ahead and re-registered
them. They are also the same version as on the other
computers.

I do have Office 2003 installed as well, but it has been
on there for a while and this problem started about one
week ago.

I went ahead and uninstalled Office 2003 and Office 97 and
then reinstalled Office 97 only...no luck.

Any other suggestions? Are their other files I need to
look at, or maybe registry settings?

Thanks again.
Mike
 
A

Allen Browne

Sorry, Mike. I've not experience the problem you describe. Hopefully someone
else will provide a suggestion.

I do use A2003 and A97, but have not experienced this issue.

Presumably the other machines are A2003? A2000 and A2002 cannot read an MDE
created by A2003. From memory, the message says something about the VBA
being corrupt.
 
M

Mike

Allen,
It gets better. I compile and compact the mdb file and
transfer it to another computer. It opens fine (although
it shows that it is no longer compiled). However, if I
make it into a MDE before I transfer it - it won't open on
the other machine.

Any idea what files are used when one builds the MDE file?

Thanks again.
Mike
 
A

Allen Browne

That behavior is also consistent with a version difference.
Are you absolutely certain the other machines are running Access 2003, not
Access 2002 (Office XP) or Access 2000?
 
M

Mike

Allen,
I appreciate all your input. I have decided to put this on
hold after spending 10 hours over the weekend dealing with
it.

I completely uninstalled all Office software and installed
Office 97 only with SR2, ODE SR2, and Jet 3.51 SP3. I
cleared the registry of all Office settings. The problem
still occurred.

The other computers don't have anything but Office 97
installed. The program was not installed as a runtime.

On one machine I did get an error code of 0x651503f7. I
searched Google and found that it involved creating MDEs
and SR1 and SR2 issues. Nothing has changed on any of the
machines over the past few months.

Anyway, I'll tackle it again at a later date. It took the
wind out of me this weekend. I'm just creating the MDE on
another computer and distributing it.

Thanks again.
Mike
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top