Office 2000 to Office 2003

[Guest]

Greetings,

Can anyone please tell me why I cannot run an executable created in Access
2000 on a system using Access 2003?

Many thanks in hope.

 

[Granny Spitz via AccessMonster.com]

Can anyone please tell me why I cannot run an executable created in Access
2000

You cannot *create* an executable in Access 2000, therefore you cannot run
one. Access 2000 isn't a compiler.

Many thanks in hope.

As in Hope, Arkansas? <g>

 

[Guest]

Many thanks for the response.

I was referring to the creation of an mde (executable) file within MS
Access, compiled within VBA.

 

[Granny Spitz via AccessMonster.com]

I was referring to the creation of an mde (executable) file within MS
Access, compiled within VBA.

An mde isn't an executable. It's a Jet database file which requires
Microsoft Access (MSAccess.exe, an executable) to open it and show Access
objects (like forms, reports etc.), run or edit queries, create or edit
tables, etc. You can run Access 2000 or newer to open the Access 2000 mde
file. You can also run other executables (Excel.exe, Word.exe etc.) to view
or retrieve data stored in the Jet database, but not objects like forms, but
only as long as there's an ISAM driver installed.

 

[Guest]

Thanks Gran.

It seems I've much to learn.

Any ideas why I cannot run the A2000 created mde on a A2003 system?

 

[Granny Spitz via AccessMonster.com]

Any ideas why I cannot run the A2000 created mde on a A2003 system?

Are you getting security warnings or error messages? If the mde file is
corrupted you'll get "unrecognized database format" or "this file has been
placed in a state by user so-and-so which prevents it from being opened ..."
In that case you need to resort to your most recent backup of the mde.

 

[Guest]

No messages. The file is greyed out, so it cannot even be clicked to attempt
to open.

A thread elsewhere on this site suggested that the mdb file needs to be
upgraded to 2003 before the mde is created. Does that sound logical to you
Gran?

 

[John Vinson]

Greetings,

Can anyone please tell me why I cannot run an executable created in Access
2000 on a system using Access 2003?

Many thanks in hope.

Since Access does not create executables, the question is unanswerable
as stated.

What did you actually create in Access 2000? An MDE file, or something
else? What is happening when you try to run it?

John W. Vinson[MVP]

 

[Klingon Coder]

No messages. The file is greyed out, so it cannot even be clicked to

attempt
to open.

Are you looking at it with windows explorer? When a file's icon is greyed
out in windows explorer it means it's a hidden file, but the name of the
file is still visible and the file can be opened.

 

[Guest]

Thanks for your response John.

I created an mde from Access 2000.

The mde runs on all but one of my other systems, i.e. those with Access 2000
installed.

The laptop with Access 2003 installed is not even recognised as an Access
file.

 

[Guest]

Thanks Klingon but that's not the problem.

Are you looking at it with windows explorer? When a file's icon is greyed
out in windows explorer it means it's a hidden file, but the name of the
file is still visible and the file can be opened.

 

[Granny Spitz via AccessMonster.com]

No messages. The file is greyed out, so it cannot even be clicked to attempt
to open.

Greyed out where? In the list of most recently used (MRU) files in Access?
(I'm guessing here, because I don't remember any item on the MRU list as ever
being greyed out.)

A thread elsewhere on this site suggested that the mdb file needs to be
upgraded to 2003 before the mde is created.

That was explaining when using Access 2003 and trying to create a *new* mde
file *from* Access 2003. The file format must be in the version you are
using, unless you have a special tool like I do. Access 2003 can only create
a new mde file from an mdb file in Access 2002-2003 format, even though
Access 2003 can open and work with Access 2000 format *and* Access 2002-2003
format files.

You already created your Access 2000 mde in Access 2000, so you can't upgrade
that mde file. But if you have the original Access 2000 mdb file, you can
convert that to Access 2003 format in Access 2003 and then create a new mde
file from that.

 

[John Vinson]

Thanks for your response John.

I created an mde from Access 2000.

The mde runs on all but one of my other systems, i.e. those with Access 2000
installed.

The laptop with Access 2003 installed is not even recognised as an Access
file.

It's possible that this machine's MDE file is corrupt. Can you copy
another that you know to be working on another machine? Or, perhaps,
use your copy of A2000 to make a fresh MDE? Be sure to open the VBA
first and compile it, correcting all errors; and compact and repair
the database before making the MDE.

A2003 should have no problems opening and using an A2000 MDE - it
works fine for me. The reverse is, of course, not the case.

John W. Vinson[MVP]

 

[Granny Spitz via AccessMonster.com]

The laptop with Access 2003 installed is not even recognised as an Access file.

On the laptop in Windows Explorer go to Tools | Folder Options, tab to File
Types, scroll down to MDE. It should be listed as Microsoft Office Access
MDE Database and set to open with Microsoft Office Access 2003.

 

[Guest]

Many thanks John.

It's possible that this machine's MDE file is corrupt. Can you copy
another that you know to be working on another machine? Or, perhaps,
use your copy of A2000 to make a fresh MDE? Be sure to open the VBA
first and compile it, correcting all errors; and compact and repair
the database before making the MDE.

A2003 should have no problems opening and using an A2000 MDE - it
works fine for me. The reverse is, of course, not the case.

John W. Vinson[MVP]

 

[aaron.kempf]

MDE / MDB is obsolete.

you should be using Access Data Projects

-Aaron