Custom Menu Disappears

[kepha12]

Windows 10 Pro, Access 2016 from office Business Premium. Converted older database to 2007-2013. When opening database on Win10 with Access 2016, it asks to enable content. Standard procedure. When enabling content my Access menu to the database functions disappears. This is not to be confused with the menu bars for the program, but a menu screen to get into the different modules of the database. The database opens fine on Win10 with Access 2013. I have added trusted location, checked the registry to make sure it is there, etc. Re installed, etc.

[CJ_London]

you need to clarify what you mean by 'disappears'

it appears then disappears?
doesn't appear at all?
the form object itself does not exist in the navigation window?

Is it the first form to open? If not what errors do you get when the code is run to open it? Is it specified as the form to display in database properties? (file>options>current database)
Is the code actually running after you enable content? Have you stepped through the code?
you only need to enable it once, so what happens if you close then reopen the db?

Are you running .accdb? .accde? accdr?

[kepha12]

FrmMenu is listed as form to display in database properties. (file>options>current database)
When opening dbase after conversion to accdb. FrmMenu displays.
Yellow security warning appears prompting to Enable Content.
Once enabling content, FrmMenu closes (disappears)
Trusted location is added for the desktop where the database resides - XXXMaster.accdb.
Close database, reopen, FrmMenu does not appear.

I am not a Dbase person. What code would I check.

I only have this issue with Office 2016 (Office 365 Business Premium.)

you need to clarify what you mean by 'disappears'

it appears then disappears?
doesn't appear at all?
the form object itself does not exist in the navigation window?

Is it the first form to open? If not what errors do you get when the code is run to open it? Is it specified as the form to display in database properties? (file>options>current database)
Is the code actually running after you enable content? Have you stepped through the code?
you only need to enable it once, so what happens if you close then reopen the db?

Are you running .accdb? .accde? accdr?

[CJ_London]

What code would I check.

if this is true

FrmMenu is listed as form to display in database properties. (file>options>current database)

then you need to check the code in the frmMenus open/load/current events

The other possibility is that the form is a popup form and if you use multiple screens it may be popping up on a phantom screen. To check, switch off or disconnect all but the primary form - does it appear then?

Also, check the form properties - is it auto centred? resized? visible?

[kepha12]

Update,
I am working with Microsoft, finally found someone willing to help that doesn't read off a script, even though Access is not their support realm.
I have installed Access 2016 Runtime at their suggestion to determine the error message, once it is determined and fixed, then the databse can be converted to .accdb from .mdb.

I am missing the MSOUTL.OLB as a reference even though the file is in the program folder. When I attempt to add the file as a reference in VBA, the file does not show in Tools > References > Available References in order to select and add it.

This is where I am stuck, how to add the MSOUTL.OLB into the object library so it can be selected as a reference.

[CJ_London]

I'm now totally confused. Your initial post said you had already converted to 2007-13. Your last post implies you have not. Your header implies you have 2016, so why do you need to install 2016 runtime? If using runtime, you will not have access to the vba editor. The MSOUTL.OLB file is a reference to Outlook, so look for a Microsoft outlook library

[kepha12]

I'm now totally confused. Your initial post said you had already converted to 2007-13. Your last post implies you have not. Your header implies you have 2016, so why do you need to install 2016 runtime? If using runtime, you will not have access to the vba editor. The MSOUTL.OLB file is a reference to Outlook, so look for a Microsoft outlook library

Ajax,

According to Microsoft: Run Access 2016 Runtime to open the database. It will show errors upon opening. Then open the database in 2013 to fix the issues with VBA before converting to accdb. I have a backup version of the database I am attempting this on while the mdb version is in production.

[CJ_London]

I don't use 2016 but previous versions of runtime don't show the errors, at best you get a 'the application has an error and will close' type of message. I can tell you that 2016 won't open early versions of mdb's - I think the earliest version is 2003. But you say you have a .accdb, so work from there. I would also hold down the shift key when you open the app, open the form that normally opens in design view, check the code module has Option Explicit at the top and the click the compile option - that will highlight any missing references.

The other thing to check is if your version of Access 2016 is 64bit - if so, there are changes you need to make to any API calls made - again, ensuring Option Explicit is at the top of every code module and compiling will identify these

[kepha12]

I don't use 2016 but previous versions of runtime don't show the errors, at best you get a 'the application has an error and will close' type of message. I can tell you that 2016 won't open early versions of mdb's - I think the earliest version is 2003. But you say you have a .accdb, so work from there. I would also hold down the shift key when you open the app, open the form that normally opens in design view, check the code module has Option Explicit at the top and the click the compile option - that will highlight any missing references.

The other thing to check is if your version of Access 2016 is 64bit - if so, there are changes you need to make to any API calls made - again, ensuring Option Explicit is at the top of every code module and compiling will identify these

**Solved***

Installed 32bit version of office. Original .mdb opened with no issues.