MDE file extension not recognized

D

Dale Fye

I just finished creating a small database and converted it to an mde file so
that I could distribute it to a few people that do not have Access installed
on their computers. When they tried to run the program, they got a dialog
box that said the file extension was not recognized, and gave them options
to search the web or select from a list.

Neither of these options worked.

I thought the whole purpose of an mde was to create a database that could
stand on its own, without the user having to have Access installed.

Dale
 
T

Tom Wickerath

Hi Dale,

I think you are confusing a run-time installation with the compiled format
(*.mde). You can distribute either a .mdb or .mde file using a run-time
installation package. In order to do so, you need to have the Developer's
Edition of Office. Just to make things totally confusing for people, the
marketing folks at Microsoft seem to give this version a different name with
every release of Access. Tony Toews has a web page that shows the various
names:

http://www.granite.ab.ca/access/developereditionversions.htm


Tom Wickerath, Microsoft Access MVP

http://www.access.qbuilt.com/html/expert_contributors.html
http://www.access.qbuilt.com/html/search.html
__________________________________________
 
A

Allen Browne

No. An MDE is not a runtime version of Access.

You can buy a developer's version of Microsoft Office that gives you the
right to install runtime Access onto client machines. More info:
http://msdn.microsoft.com/office/technologyinfo/devtools/accessextensions/default.aspx

An MDE is different. An MDB file contains two versions of the code you
write:
- a text version (what you see and edit),
- a compiled version (what executes on the processor.)
An MDE file contains only the compiled version. As a result, users cannot
view your code, or create/alter forms or reports, and the code cannot become
decompiled.

It is therefore common for developers to distribute an MDE to end users, but
an MDE cannot execute without Access.
 
P

Pat Hartman\(MVP\)

Sorry but the .mde is simply an .mdb with the source code removed. There is
no way to run an Access application without having Access installed on the
computer. If your clients do not wish to purchase retail versions of
Access, you can purchase the MS Office extensions for Visual Studio which
includes what used to be called the "developer's edition" of Access. In
reality, this is a license to distribute a runtime version of MS Access and
the packaging and deployment wizard which allows you to create an
installation package. This package includes your .mdb or .mde (unaltered),
any other files your application needs to install, plus an optional copy of
MS Access which will be installed on the client PC so it can run your
application.
 
D

Dale Fye

Allen,

I purchased an MSDN subscription several years ago. Installed Office XP and
have been using that. After getting your email, I looked in the MSDN disks,
and I have a copy of Office XP Developer but it is dated July 2001, and when
I try to run it, it indicates that I have newer versions of the software
than is required by the disk. Any idea how I can get the SPs to Office XP
developer so I can install it over my current copy of Office XP?

Dale
 
A

Allen Browne

Actully, Dale that's the version I use too--the XP Dev from MSDN.

You can download the runtime updates from Microsoft. You do need to install
Access 2002 on the computer, even if you have 2003. And you *must* use A2002
to create the MDE. Even though the file format for Access 2002 and 2003 is
the same, the binary (compiled code) is different, so if you create the MDE
in A2003, it will not run under the runtime 2002.
 
D

Dale Fye

Allen,

I have the various sheets that contain a bunch of the MSDN product keys, but
cannot find any reference to the Office XP Developer product key do you
have any idea how I can find out what the key is from Microsoft. These
sheets from MSDN list the
msdn.microsoft.com/subscriptions/resource/support.asp as the page to go to
to get the keys, but these are over 3 years old, and that URL no longer
exists. Last time I talked to the MSDN office was a couple of years ago,
before my hard drive crashed. I had their phone number and all that in
Outlook at the time, but have lost it.

Dale
 
A

Allen Browne

Hmm. That will be a problem is the sub is not current. From memory, in the
early days the sub was written on a sticker or insert in the pack, along
with the Office one. If you don't have that, I'm not sure what to suggest.
 
G

google3luo359

Allen said:
Actully, Dale that's the version I use too--the XP Dev from MSDN.

You can download the runtime updates from Microsoft. You do need to install
Access 2002 on the computer, even if you have 2003. And you *must* use A2002
to create the MDE. Even though the file format for Access 2002 and 2003 is
the same, the binary (compiled code) is different, so if you create the MDE
in A2003, it will not run under the runtime 2002.
Click to expand...


On a related topic.
A couple of years ago I tried to show someone an Access 2000 .mde file.
It was written on a Win 98 system.
I can't remember if they were using WinXP or Access 2003 or higher but
the .mde file wouldn't open on their computer. I had to run it on a Win
98 computer they had in another office.

What would I need to do to run a Win 98 .mde file on a later system?

Also, will I be able to split my Access 2000 .mdb file and have it run
on later access versions?

Thanks!

Ric
 
A

Allen Browne

If we are talking runtime installation, some system files may be specific to
the Windows family, i.e. you need to use the same family of Windows to
create the runtime.

Splitting is fine--normal practice.
 
G

google3luo359

Allen said:
If we are talking runtime installation, some system files may be specific to
the Windows family, i.e. you need to use the same family of Windows to
create the runtime.

Splitting is fine--normal practice.
Click to expand...


Thanks Allen.
 
Top