Re: Converting Access 97 MDE to Access 2003
- From: "Allen Browne" <AllenBrowne@xxxxxxxxxxxxxx>
- Date: Thu, 17 Nov 2005 09:35:41 +0800
Ah: your MDB and MDE are 2 different things (back end and front end), not 2
versions of the same thing.
An MDB contains 2 versions of the code in it:
- a text version (what you read and edit), and
- a compiled version (the binary that actually executes.)
An MDE contains only the binary. You cannot read or edit the code, and you
cannot convert between versions. It therefore needs to continue to exectue
under the original version, unless you can find the original MDB front end
that the MDE was made from. If you can find that, you can convert it to the
new version, and then use the new version to make another MDE.
--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.
<melickas@xxxxxxxxx> wrote in message
news:1132158919.586875.244450@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> If we open the MDB in Access97, there is no code -only the tables since
> this is the backend. We can create a new Module, and do as you
> instruct, but there is nothing to compile since there is no code. The
> code is in the MDE but the MDE cannot open in Access03 -get the "can't
> convert or enable MDE file" error. Please explain. Thanks
>
.
- Follow-Ups:
- Re: Converting Access 97 MDE to Access 2003
- From: melickas
- Re: Converting Access 97 MDE to Access 2003
- References:
- Converting Access 97 MDE to Access 2003
- From: melickas
- Re: Converting Access 97 MDE to Access 2003
- From: Allen Browne
- Re: Converting Access 97 MDE to Access 2003
- From: melickas
- Converting Access 97 MDE to Access 2003
- Prev by Date: Re: Converting Access 97 MDE to Access 2003
- Next by Date: Re: Upsizing Wizard
- Previous by thread: Re: Converting Access 97 MDE to Access 2003
- Next by thread: Re: Converting Access 97 MDE to Access 2003
- Index(es):
Relevant Pages
|
Loading