MDE File creation --- Access 2003

[Grumpy Aero Guy]

I am unable to create an mde file from a Access 2003 database.

I have read KB 814858, and tried the decompile procedure indicated in the
article, to no avail---unfortuneately.

This is a good size database (88,000+ records), 96Mb, or so. I have
compacted and repaired db several times---each time successfully.

This was an Access 2000 database in its previous life, converted to A2003.
A2000 would create the MDE without problem.

Any other wisdom out there?

I appreciate your time and effort in advance.

 

[Van T. Dinh]

My guess is that the file is still in A2K file format. A2K3 opens database
in A2K file format without any problem. However, it can only convert a
database to MDE if the database is in A2K3 file format.

Try convert the database file to A2K3 file format first, check for Compile
errors and then make MDE.

HTH
Van T. Dinh
MVP (Access)

 

[Grumpy Aero Guy]

Sorry, I didn't mention that I did convert it 2003 prior to the mde attempt.
I apologize for not mentioning that.

I was aware that 03 would open it in 00 format and that the conversion was
necessary.

Still no luck though.....

 

[Van T. Dinh]

You did, actually. I just wanted to be sure.

Did you get any error message?

Also, I would split the database to Front-End and Back-End. The Back-End
can stay as MDB format and you only neeed to convert the Front-End to MDE.

HTH
Van T. Dinh
MVP (Access)

 

[Arvin Meyer]

Frank (or should I address you as Grumpy?),

Try this:

1. Create a new, empty, database in A2003 format.

2. Import all the objects from your present database.

3. Make sure that all the necessary references are set (from any code window
choose: Tools ... References)

4. Compile the database. (from any code window choose: Debug ... Compile)

5. Fix any errors that appear from compiling.

Now try to make the MDE
--
Arvin Meyer, MCP, MVP
Microsoft Access
Free Access downloads:
http://www.datastrat.com
http://www.mvps.org/access

 

[Grumpy Aero Guy]

No error.....app just hangs... have to go to task manager to kill access.

front end / back end..... I'll have to check into trying that.

Thank you VERY much for your input.

Best Regards,

 

[Van T. Dinh]

In the mean time, I would recommend Arvin's procedure.

Van T. Dinh
MVP (Access)

 

[M.L. Sco Scofield]

You never mentioned. Have you been able to get a clean compile of the VBA code?

Next, have you looked for "Missing" references at Tools/References while in the VBA IDE?

If you can get a clean compile in Access 2000 with this database, my money is on a bad reference.

If it's neither of these problems, I'd try making a new mdb in 2002/2003 format and then import all of the objects from your other
database.

Good luck and please report back.

--

Sco

M.L. "Sco" Scofield, MCSD, MCP, MSS, Access MVP, A+
Useful Metric Conversion #16 of 19: 2 monograms = 1 diagram
Miscellaneous Access and VB "stuff" at www.ScoBiz.com

 

[Grumpy Aero Guy]

Have you been able to get a clean compile of the VBA code?
yes

Next, have you looked for "Missing" references at Tools/References while in
the VBA IDE?
i'm on it

I'd try making a new mdb in 2002/2003 format and then import all of the
objects from your other database

OK.....I'll report back...


--


Frank Bachman
(Grumpy Aero Guy)

You never mentioned. Have you been able to get a clean compile of the VBA code?

Next, have you looked for "Missing" references at Tools/References while in the VBA IDE?

If you can get a clean compile in Access 2000 with this database, my money is on a bad reference.

If it's neither of these problems, I'd try making a new mdb in 2002/2003

format and then import all of the objects from your other

 

[Grumpy Aero Guy]

SUCCESS.....

I created a new '03 database as recommended.

Imported everything.....recompiled....made mde.....

(All is well)

My sincere thanks to all who assisted. I am a happy (no longer grumpy)
camper.

THANKS TO ALL !!!!

 

[Tony Toews]

SUCCESS.....

But as Van states you really want to check into a FE/BE system. Much
reduced chance of corruption.

You want to split the MDB into a front end containing the queries,
forms, reports, macros and modules with just the tables and
relationships. The FE is copied to each network users computer. The
FE MDB is linked to the tables in the back end MDB which resides on a
server. You make updates to the FE MDB and distribute them to the
users, likely as an MDE.

See the "Splitting your app into a front end and back end Tips" page
at my website for more info. See the Auto FE Updater downloads page
at my website to make this relatively painless.. It also supports
Terminal Server/Citrix quite nicely.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm

 

[Grumpy Aero Guy]

That's good info......

My db is a stand-alone app.

BUT....I do, on occasion, build client-server type apps with access. I'll
keep this advice handy.

Thanks for your input.