Can't make a MDE file in access 2003 but can in Access 2000 even after converting to 2K3...Please he

[Ralph Malph]

I have a database that I created in Access 2003. I wanted to make it a
MDE. Since my 2003 access made the file format version 2000 by default
I was told by the system that I had to convert it to a 2003 file in
order to compile it into MDE file. I did this and then tried to turn
it into a .MDE file. When I did this Access went into never never
land. It just sat there with the hour glass until I used Task Manager
to kill the program. When I took the same file, prior to conversion to
an Access 2000 system it compiled it into a .MDE file in less than 30
seconds. What could be causing the problem. I have tried this on
several dif. computers. When I try to create the .MDE in 2003 the
program seem to make database file for backup called db1.mdb. This it
has no problem doing but the file does not open, and the .MDE file is
never created. I have to kill Access via task manager in order to stop
access.

Any ideas as to why this is happening ?

Thanks for any and all help,

Ralph Malph

PS... How do I get the form to startup WITHOUT the rest of Access. I
would like the form to start but not see the Access toolbars etc. Just
the form which has all the controls it needs.

Thanks again

 

[Guest]

It happen to me recently, and I couldn't understand why, when I ran
compilation on the mdb, it gave me no error, but it open some form and then
I got a message if I want to save this form.
After a while I press the yes button to save that form, and every thing
worked perfect agan.
MyBe that is your problem, try it, compile your code and see if any object
opens.

 

[Ralph Malph]

Ofer,

I get no other objects etc opening, Just an hour glass and a copy of
the DB which if I run will say that it is missing/or the VBA part of
the program is corrupt. Of course I have to kill the process, befor I
can open the new .mdb file. The system also slows to a crawl as the
hung process eats up all my CPU resorces. I am als
compacting/repairing the DB before and after conversion from 2000 to
2003 with no error messages.

Thanks for trying to help,

Ralph Malph

 

[Guest]

What I meant is, don't create an mde file yet.
Compile the mdb, open code > debug > compile (mdbName).
Now do you get any object open. and it ask if you want to save it, if so
then save it and try to create mde.

 

[Albert D.Kallal]

After you save the file in a2003 format, try compiling the code...
(just hit ctrl-g, and then go debug->compile).

Does the application compile ok? ...any errors?

So, BEFORE you try making a mde, try compiling the application.

In fact, virtually everytime I make a code change, I do a compile.

PS... How do I get the form to startup WITHOUT the rest of Access. I
would like the form to start but not see the Access toolbars etc. Just
the form which has all the controls it needs.

I have a working sample that hides all of ms-access. You can download and
try it here:
http://www.members.shaw.ca/AlbertKallal/msaccess/DownLoad.htm

(grab the 3rd one...ms-access interface hidden link).

Note that the above hiding does not take any code, but simply uses the
tools->startup options. (so, give the sample a try, and then take a look at
the options set in that example).

 

[Ralph Malph]

I seemed to have no errors nor any request to save anything when
compiling, which by the way I was not doing. I had defiantly
misunderstood your previous suggestion. It however did not fix the
problem.

Thanks any way,

Ralph Malph

 

[Ralph Malph]

After you save the file in a2003 format, try compiling the code...
(just hit ctrl-g, and then go debug->compile).

Does the application compile ok? ...any errors?

So, BEFORE you try making a mde, try compiling the application.

In fact, virtually everytime I make a code change, I do a compile.


I have a working sample that hides all of ms-access. You can download and
try it here:
http://www.members.shaw.ca/AlbertKallal/msaccess/DownLoad.htm

(grab the 3rd one...ms-access interface hidden link).

Note that the above hiding does not take any code, but simply uses the
tools->startup options. (so, give the sample a try, and then take a look at
the options set in that example).

 

[Albert D.Kallal]

Ok, so the a2003 compiles no problem.

Hum, I would try creating a blank database, and then import everything into
this database. Then, try compiling this new a2003. And, if you get that far,
then try creating a mde....

And, while you are at it, perhaps try build a super simple mdb (2003), from
scratch.....and see if that can become a mde. (perhaps you have a bad
install or something).