Compile Error Not Showing What Is Error

  • Thread starter Thread starter Caie
  • Start date Start date
C

Caie

Hi wizards and muggles,

I'll give you the history of what I did:

1. The "make MDE" button was greyed out for the database in question.
I traced this as being the caused by the fact that the database was
in Access 2000 format but being edited in Office 2002.
2. I converted it to Office 2002 and attempted to make an MDE. This
failed with the message "Microsoft Access was unable to create an MDE
database".
3. I then used the VBA editor to try and compile the project. This
fails with the message "User-defined type not defined". But fails to
specify which module/form that is raising the compile error.

Argh!

I have checked the References and there are none "missing" whatsoever.
We're talking serious amounts of code here and if possible I'd like
to avoid exporting invididual modules to try and locate the error that
way. Does anyone know why VB wouldn't show the exact statement(s)
that are stopping the compile? Is it something as simple as an option
in tools that I haven't got turned on (run-time errors are flagged
individually)? Any help is gratefully recieved.

Caie
 
The Debug should highlight the line of code that errors out.

Post that line of code.

HTH
Van T. Dinh
MVP (Access)
 
Van,

Thanks for the reply - but the essence of the problem is just this -
the compiler doesn't highligh the line of code producing the error(!)
- the dialog box just pops up with the error "User-defined type not
defined" and does not show anything else.

Caie
 
Van,

Thanks again. I had seen all those MSDN advice pages before and had
known about the most common cause of the message (DAO to ADO issue)
before starting the project. It seems that Access isn't going to let
me know what the problem is.

I have managed to stop the messages (and make an MDE after compiling)
by importing all the forms, reports, queries and modules into a brand
new project. Looks like this may be a bug in Access?

Thanks for trying

Caie
 
Back
Top