Form not saved in a fully compiled state

[Guest]

am using Access 2K - db is 9KB, lives on a network and i have 2 assistants
doing data entry

when i run the anaylze tool i get "Form not saved in a fully compiled state"

i'm not entirely sure what this means, or how/if to go about compiling

i do routinely run the compact/repair utility

 

[Guest]

sorry, that's Access 2002 i'm using

 

[John Vinson]

am using Access 2K - db is 9KB, lives on a network and i have 2 assistants
doing data entry

when i run the anaylze tool i get "Form not saved in a fully compiled state"

i'm not entirely sure what this means, or how/if to go about compiling

i do routinely run the compact/repair utility

Try getting your assistants out of the database. Type Ctrl-G to open
the VBA editor and select Tools... Compile <your database>. If you get
any VBA errors, fix them.

If that doesn't help, your database may be corrupt. See

http:/www.granite.ab.ca/access/corruptmdbs.htm

for suggestions.

If you're sharing the same database among three (or even two) users,
you should REALLY use the Database Splitter Wizard to put the tables
in one 'backend' database and the forms and user interface in three
'frontend' databases, one for each user. This will greatly reduce this
kind of problem.

John W. Vinson[MVP]

 

[Guest]

thanks for the help!

after compiling/re-running the analyzer i got:

Application: save your application as an MDE file

and

Form: use an option explicit statement - the notes section cautions that
this requires me to declare all varialbe explicitly. (not that i knew i'd
declared them implictitly *grin*)

any thoughts?

 

[John Vinson]

thanks for the help!

after compiling/re-running the analyzer i got:

Application: save your application as an MDE file

Huh!? What "analyzer", and where did I suggest running any analyzer?

and

Form: use an option explicit statement - the notes section cautions that
this requires me to declare all varialbe explicitly. (not that i knew i'd
declared them implictitly *grin*)

Open your Form in design view.
Type Ctrl-G or click on the "code" button on the toolbar to open the
Form's VBA module.
Scroll up to the very top.
Type

Option Explicit

before the first Sub line.

This will make the compiler enforce the good programming practice of
explicitly using a Dim variable As Type line for every variable used
in your code. If you're not Dim'ing variables, Access will assume you
want them to be Variants - which are big, expensive, often
unnecessary, and sometimes WRONG.

Then select Debug... Compile <your database> from the menu. If you've
been coding without Dim'ing your variables you'll get a whole raft of
error messages. Dimension your variables and keep compiling until you
get no more errors.

Then see if this "fully compiled" error goes away!

John W. Vinson[MVP]