Form prevents conversion to mde

[Guest]

Good Day!

I am getting error pop-ups whenever I convert my database to an mde file. It
is already formatted to Access 2002. I tried isolating the problem by
removing objects that might have been causing the error - and found out that
my main form seems to be the trigger of the error. After deleting the main
form I successfully created an mde out of my database ... all other forms,
queries,tables and objects were successfully converted, the problem now is
its useless w/out the main form.

I tried to go around it by copying and pasting the form back to the mde but
it will not allow it. How do i find out what is causing Access to fail mde
conversion due to a form?

Details: Access 2002 , format:2002 .
The form's data source is a query, with a subdatasheet. The database is an
FE with a BE on a network drive. The form contains a lot of controls with
events - some codes I inherited from previous administrators, some were
recently created.

Thank you very much.

 

[Albert D.Kallal]

Hopefully, we got a copy here.

take your original mdb, and try to compile the code....

(just go ctrl-g, and then while looking at code go debug-compile).

Note that as a general rule, my fingers after editing code will go ctrl-s,
and then alt-d <enter key>

The above keys happens so often, and so fast that I can't even remember
doing it anymore. The trick here is to always compile your code. If you
don't compile code, then often inteli-sense will stop working. Only until
you fix all errors, does it come back.

Worse, if you edit some code, and close the code window, then it will
re-open when you return to the code window (ms-access still thinks you need
to work on that code since you did not compile it). So, not compiling your
code means all kinds of code windows open up when you return next time. And,
not compiling means that inti-sense often breaks, again, it can't work when
you got errors. And, last, but not least, with errors in your code, you
can't make a mde..

So, try compiling your code to find the error(s), and fix them (this is why
a mde is such a good idea, as you don't want distribute code with syntax
errors in it).

Once your code compiles...then you should have no problem making a mde...

 

[Guest]

Thanks that worked, Compiling saved the day. i think it should be part of all
instructions for creating an mde file. For other users who have the same
problem,
on the module window simply click ctrl-g, select Debug from menu, then
select compile "database name".

Thank you very much.