MDB file acts like mde after running an mde application?? 1

[steve728]

Something odd is happening here. After I open and close a recently installed .mde application, I open a previously working .mdb file. It now runs exactly like a .mde file with limited menu items, etc. The only way I can get the .mdb file working again properly is to reinstall office 2000. Could it be that the newly installed .mde application is a higher version and therefore, somehow corrupts the mdb application. I need help.

Steve G.

 

[KornGeek]

Does the mde install a run-time version of Access? I have seen the run-time version overwrite the full version, and that sounds like what is happening.

 

[steve728]

Thank you for replying so quickly! Do you know if it is possible for an mde application to install the runtime version everytime the application is started? I think you may have helped me find the problem. How can I stop the overwriting from happening? You're going to get a star!

Steve G.

 

[KornGeek]

Where did the mde come from? How do you launch it?

I've seen some strange interactions between the run-time version and the full version. It wouldn't surprise me to find out that you are launching the mde from a shortcut that references the run-time version, and this is somehow setting it as the default version of Access.

 

[steve728]

I'll check outthe desktop icon command line. You get a star Cyber Buddy!

 

[steve728]

Hey good friend,

Look what I found inside the desktop icon that calls the new application:

"C:\Program Files\Microsoft Access Runtime\Office10\MSACCESS.EXE" /runtime /profile "Falcon 2000" /wrkgrp "C:\F2000\System.mdw" "C:\F2000\Falcon.mde"

Just like you said!
You get a star alright!

Steve

 

[KornGeek]

Thanks for the star.

I'm not sure why it would be killing the full version of Access, but as I've said, I have seen that behavior before. Maybe somebody with more insight into this can shed some light on the subject.

As far as fixing this, change the shortcut so that the fist part points to your version of Access rather than the runtime version and remove the /runtime switch. Everything should work at that point.