Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion GroupsFormsForms ProgrammingQueriesModules / DAO / VBAReports / PrintingMacrosDatabase DesignSecurityConversionImporting / LinkingSQL Server / ADPMultiuser / NetworkingReplicationSetup / ConfigurationDeveloper ToolkitsActiveX ControlsNew UsersGeneral 1General 2
Access DirectoryToolsTutorialsUser Groups
Related Topics
SQL ServerOther DB ProductsMS OfficeMore Topics ...

MS Access Forum / Conversion / July 2003

Tip: Looking for answers? Try searching our database.

Can't Convert Access 97 MDE File

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Tony - 22 Jul 2003 19:39 GMT
I have an application that we have been unable to get to
work on Access 2000.  I have created an MDE file and used
office developer tools to create a run time file for a
machine with Access 2000 on it.

I get the "You can't convert or enable an MDE file" when I
go to run it.  

I know there is something you can change in the Office
Developers Setup Wizard to get this to work, but I forgot
what it was.  Does anyone know.

Thank You in Advance

Tony
david epsom dot com dot au - 23 Jul 2003 06:22 GMT
No, you can't convert an MDE.

You have to use Access 97 with the 97 MDE,
and A2K MDE with Access 2000.

(david)

> I have an application that we have been unable to get to
> work on Access 2000.  I have created an MDE file and used
[quoted text clipped - 11 lines]
>
> Tony
Greg Homyer - 25 Jul 2003 01:18 GMT
I would imagine that you should install the Access 97 runtime file in a
directory other than the Microsoft Office directory.  You have to set up
your install and app to make sure that Access 97 runtime is running your
app, rather than Access 2000.  If I remember correctly, unless you do that,
when Access 2000 is detected, your Access 97 runtime won't be installed.   I
have to say I am not entirely certain anymore because I quit using the Set
Up Wizard for Access 97 and PDW in Access 2002 due to conflicts among
versions during installs, etc., which the MS tools do not handle well.  I am
sure others who are still using the MS tools will fill you in more
completely.

If this is a one time deal, you will find a workaround, but if you intend to
be installing runtimes on machines far and wide that may have other versions
of Access present, see www.sagekey.com

Regardless, you can't convert an .MDE file, anyway.  Any changes or
conversion, regardless of Access version must be done on the .mdb   After
changes or a conversion, then make a new .mde
Always keep a copy of the last .mdb in case you want to make changes.

--
Greg Homyer

> I have an application that we have been unable to get to
> work on Access 2000.  I have created an MDE file and used
[quoted text clipped - 11 lines]
>
> Tony
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.