Hi Jeanette

Sorry for not getting back sooner but work got in the way.

Now that I have converted the database what should the new references be? it
looks like I still have the same old ones.

I now get this new error message

Microsoft can not find the macro "mnuMain" the macro groups don't exist or
it is new and has not been saved, then it talks about the macorgroup that was
saved
I must specify the same macroname in the argument???

Any ideas on this?




"Jeanette Cunningham" wrote:

Option Explicit
Option Compare Database

should be in the order

Option Compare Database
Option Explicit


-------------------------
macros - that's fine. You have checked for macros and there are no macros.
That is one less thing to check for errors.

----------------------

About converting to A2003
One easy way that I do conversions is to create a new blank database in the
newer version and be sure to set 'Track Name Auto correct' to No.
So create a new blank database in A2003, go to Tools | Options | General tab
and set Track name autocorrect to no.

Do you have linked tables?
If you do, use the new blank database you just created and import the tables
into it (don't link them).

Then create another new blank database for the front end.
Link the tables to the new database, then import all the other objects -
queries, forms etc.

If you don't have linked tables, just create one new database as described
above.
Import everything from the 97 database to the new one.

After you finish the import do a compile.
Check for the correct references.

You will now have an A2003 version of your database and can continue on with
fixing any errors.




Jeanette Cunningham MS Access MVP -- Melbourne Victoria Australia

"Brent" wrote in message
news
Hi Jeanette

This is where the compiler stops when I run debug on the Modules of the
database that I have converted to 2003. It just stops on this line and
does
not give an error message.

your previous message:
I don't have Access 2000 on my computer anymore

The next thing to check is the code.
What code do you have when the database opens? It tell me Microsoft access
can not find the macro "mnuMain" I lkkoed and there are no macros in this
database not ever Auotexec macro
Is there an autoexec macro?
What code is on the main menu form? Do you want me to post all of the code
I
found for the form? it is long.
How do I put break points on the subs and functions?

Gina asked that on the top of every module had
Option Explicit
Option Compare Database

Yes they do however they are in reverse order, does this matter?

Thanks again for all your help. This post maybe confusing, let me know





"Jeanette Cunningham" wrote:

Is this function the spot where the compiler stops and gives an error?
What error does it give?


Jeanette Cunningham MS Access MVP -- Melbourne Victoria Australia



"Brent" wrote in message
...
Here is me first debug problem that is identified

Public Function CMD_EnableCommandBarCtl(pcbr As CommandBar, pstrTag As
String, fEnable As Boolean) As Boolean

This shows up in each Module I debug. Does this help or is their more
to
this that I need to post?

"Gina Whipp" wrote:

Brent,

Things I would check...

1. Please list the References you have set and the order in which
they
appear. Because Access 97 had some References that were unnecessary
to
future versions, once you post what you have one or two may need to be
eliminated to 'fix' the Main Menu.

2. Make sure at the top of every module appears...

Option Explicit
Option Compare Database

This will insure the are no undeclared variables that are causing the
problem.

3. Go into an module window and Debug - Complie and fix any errors
that
might appear.

--
Gina Whipp

"I feel I have been denied critical, need to know, information!" -
Tremors
II

http://www.regina-whipp.com/index_files/TipList.htm

"Brent" wrote in message
...
Thanks Jeanette
When I opened the code and check the references the Microsoft DAO
3.6
Object
Library was already checked, I compacted and repaired a few times
and
the
result is the same, the Main Menu Form will not open it still thinks
I
have
not converted to a newer version. Could there be something in the
code
somewhere that is causing this? if so where can i find it?

"Jeanette Cunningham" wrote:

Hi Brent,
When you have the database open and the main form open in design
view,
open
the code window and check the references.
You will need to select the Microsoft DAO 3.6 Object Library as a
reference.
After you set that reference and close the references dialog, do a
compile
and fix any errors until the code compiles.


Jeanette Cunningham MS Access MVP -- Melbourne Victoria Australia



"Brent" wrote in message
...
I have just converted a database from version 97 / 2000 to MS
Access
2003.
The Main menu form will not open, I get a message that I must
convert
to a
newer version that 97 / 2000 and then it closes the database
down. I
have
converted the database. This is the only form that will not open.
I
open
the
database using the shift key and the main form will open in
design
view.
Can
someone help with this problem?

Thanks