Main Menu Form Will Not Open

  • Thread starter Thread starter Brent
  • Start date Start date
B

Brent

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
 
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
 
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?
 
The next problem with A2000 is that it had many service packs - do you have
them all installed?

The next thing to check is the code.
What code do you have when the database opens?
Is there an autoexec macro?
What code is on the main menu form?

One way to test the code is a method like this that I have used-->
Open your database with the shift key.
Open the main form in design view and put break points on the subs and
functions.
Close the main form.
Now open the main form in form view from the database window.
When the code window opens, step through the code.
Note the first error. I don't recommend making any changes to code in break
mode, so stop the code and then fix the code.
Keep testing and fixing until it works.


Jeanette Cunningham MS Access MVP -- Melbourne Victoria Australia
 
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
 
First of all thanks to Jeanette and Gina for your help with this problem.

I will start with listing the References I have checked in order from first
to last:

1. Visual Basic for Applications
2. Microsoft Access 10.0 object Library
3. OLE Automation
4. Microsoft DOA 3.6 Object Library
5. Microsoft Active X Data Object 2.5 Library

Now I will try some of the other suggestions and this may take some time as
I am not good with Modules and code issues.

I will post back results or if I have problems with the codes
 
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?
 
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
 
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.

Re: 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
 
Gina

Yes, I did convert the database to 2003 but that seems to be the problem the
database done not think I have. It keeps asking for me to use a newer program
97 or newer and I am.
 
Gina

Gina Whipp said:
Brent,

Is this the line that is highlighted in yellow?
Click to expand...
There is no yellow highlighted line the line above was in blue

Also, copy/paste the rest of the module here. This is from the form code


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

Dim ctl As CommandBarControl

On Error GoTo Err_CMD_EnableCommandBarCtl
Call RecordTrace("basCmdFunctions", "CMD_EnableCommandBarCtl", pcbr.Name)
CMD_EnableCommandBarCtl = False

Set ctl = pcbr.FindControl(msoControlButton, Tag:=pstrTag,
Visible:=True, Recursive:=True)
ctl.Enabled = fEnable

CMD_EnableCommandBarCtl = True

Exit_CMD_EnableCommandBarCtl:
Exit Function

Err_CMD_EnableCommandBarCtl:
Select Case Err
Case 91 'Control doesn't exist
CMD_EnableCommandBarCtl = True
Case Else
Call GlobalError("basCmdFunctions" & ".CMD_EnableCommandBarCtl")
End Select
Resume Exit_CMD_EnableCommandBarCtl

End Function

Hope this helps
 
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
 
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?
 
There are 3 references you need for A2003
Visual basic for applications
Microsoft Access 11.0 Object Library
Microsoft DAO 3.6 Object Library

When you imported all the objects, you may have ommitted the menus.
Go back to the import screen and under options select Menus and Toolbars.
Don't select any tables, queries etc, just the menus and toolbars.
See if this fixes the problem.

What is the name of the form that should open when the database opens?
Have you put this form as the startup form in the database options | Tools |
Startup
Display Form/Page:


Jeanette Cunningham MS Access MVP -- Melbourne Victoria Australia
 
Hi Jeanette

Here is the code where the yellow highlight starts, I just found it. Do you
see anything in the code that is causing the problem? It looks to me like
there might be something here as it tells to stop application if !!!! The
form is in the startup

Public Function APPL_StartApplication() As Boolean

Dim fldEntityName As Field
Dim fldEntityPath As Field
Dim intI As Integer
Dim lngNumDatabases As Long
Dim qdfEntity As QueryDef
Dim rstEntity As Recordset
Dim strMsg As String

On Error GoTo Err_APPL_StartApplication
Call RecordTrace("basApplFunctions", "APPL_StartApplication")
APPL_StartApplication = False

TryRelink:
Set rstEntity = Nothing
If CMD_GetVersion() < "8.0" Then
strMsg = gconSystemTitle & " must be run with Microsoft Access 97 or
later"
MsgBox strMsg, vbOKOnly + vbCritical, gconSystemTitle
Application.Quit A_EXIT
End If

Set gwrk = DBEngine.Workspaces(0)
Set gdb = CurrentDb

Set qdfEntity = gdb.QueryDefs("qselEntityDatabases")
Set rstEntity = qdfEntity.OpenRecordset
With rstEntity
.MoveLast
.MoveFirst
lngNumDatabases = .RecordCount
Set fldEntityName = .Fields("EntityName")
Set fldEntityPath = .Fields("EntityPath")
End With
ReDim gdbLinked(1 To lngNumDatabases)
intI = 0
With rstEntity
.MoveFirst
Do While Not .EOF
intI = intI + 1
Set gdbLinked(intI) = DBEngine.OpenDatabase(fldEntityPath & "\"
& fldEntityName)
.MoveNext
Loop
.Close
End With

'Set startup properties of database
If CMD_IsItMDE(CurrentDb) Then
Call CMD_SetStartupProperties
End If

APPL_StartApplication = True

Exit_APPL_StartApplication:
Exit Function

Err_APPL_StartApplication:
Select Case Err.Number
Case 3044, 3051, 3043
MBX_Ok "Unable to open the database " & fldEntityPath & "\" &
fldEntityName
If Not CMD_OpenForm("frmEntitymaintenance",
plngWindowMode:=acDialog) Then Resume Exit_APPL_StartApplication
Resume TryRelink
Case 10001 'Error in called procedure
Case Else
Call GlobalError("basApplFunctions" & ".APPL_StartApplication")
End Select
Resume Exit_APPL_StartApplication

End Function

Thanks again for all your help
 
Here are the steps to debug this code:
Find the line Call RecordTrace("basApplFunctions",
"APPL_StartApplication")
and click in the very far left margin for this line to set a break point -
when it is set you will see the whole line coloured red.
Save and close the code window.
Close the startup form if it is open.
Now open the startup form.
The code will stop at the break point you set.
Now press F8 to step through the code.


Post back with results.


Jeanette Cunningham MS Access MVP -- Melbourne Victoria Australia
 
Jeannette

Here is the first place the code stoped at I pressed F8

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

Compile error user-defined type not defined

I can not proceed pass this line.

Thanks
 
Back
Top