Blank Window Pops After DB Opens and before Main Menu Displays

[maxis]

We're running Office 365 Pro and Windows 7 and Windows 10. This appears to only
happen with Windows 7, or happens so fast with Windows 10 we don't see it. Our
MS ACCESS application is a split database, and when we open the App we have a
DISPLAY FORM equal to Main Menu XYZ. Normally when we open the App we see the
normal MS Access Window with the menu bars, then the Main Menu XYZ opens in the
center of the MS Access Window. But recently we started getting a blank window
popping up between those two steps. The new blank window is the same size as the
MS Access Window and stays for 2 to 5 seconds, and the MS Access Windows seems
to go away because this new blank window displays over it. Then the MS Access
screen comes back with the Main Menu XYZ displaying just like it normally does.
It's just the new blank window step, which appears to have a WINDOWS/OFFICE
border around it (not a MS ACCESS FORM type border around it). ALSO, and I
attached the screen prints below, the APPLICATION ICON in the status bar is
doing the same thing. We see the MS ACCESS ICON, then the BLANK WINDOW ICON,
then the APP ICON. Normally we only see the MS ACCESS ICON and the APP ICON
(Eagle).

The issue is we're not even sure where this new WINDOWS is
coming from. Could it be some type of OFFICE 365 AUTHORIZATION, or SHAREPOINT
(we do have to LINKED SharePoint LISTs), or some ADD IN?



The fact the ICON changes on the Status Bar seems to say it's
something OUTSIDE MS ACCESS that is switching in and out, but that's the $64K
questions.

We can't even figure out what to "google" because
we're not sure where the blank screen is coming from, but we don't think it's
the APP doing it (we haven't had any recent coding change). We've put in breaks
and know it's happening BEFORE the LOAD EVENT of the DISPLAY FORM Main Menu XYZ.
Also, if we open the database (shift-key) and manually open Main Menu XYZ the
blank screen doesn't display. And in Windows 10, it doesn't
seem to happen or happens so fast that we don't see the ICON
change.

Any HINTS/CLUES would be appreciated. I
attached the APP ICONS on the status bar. The 2nd one shows the BLANK WINDOW
that's coming up.

[isladogs]

I think you mean the taskbar at the bottom of the screen.
As an experiment try disabling your startup code. Remove the startup form. Rename the autoexec macro if you have one.
Then try using the shift bypass whilst you open the database.
Does the issue go away? If so the issue was in your startup code
Now open your startup form manually. Does the effect occur now?

[maxis]

There is no AUTOEXEC, we use DISPLAY FORM in OPTIONS and select the XYX Main Menu FORM. In the LOAD EVENT we do "stuff". When you hold the shift-key down and start the XYZ Main Menu FORM manually it does NOT show the blank screen. We've put break points in the code and it appears that the "blank screen" happens BEFORE the LOAD EVENT, but the LOAD EVENT is the only place with have any VBA code. That's the mystery, we can't even figure out where to stop the code because we don't even know what the blank screen is trying to do or where it comes from. Is it a HELP screen, a SharePoint integration screen, an OFFICE cert type screen? The reason we mentioned the taskbar/status bar on the bottom that normally displays all the APPLICATION ICON that are open, is because normally anything to do with a FORM inside the database would never change the APPLICATION ICON on the taskbar. That's an application level type deal, so how does the APPLICATION ICON change to a blank screen if it wasn't SOMETHING ELSE trying to OPEN? Maybe our logic is wrong. Hoping someone out there has seen something similar. THANK YOU!

[isladogs]

We've put break points in the code and it appears that the "blank screen" happens BEFORE the LOAD EVENT, but the LOAD EVENT is the only place with have any VBA code.

You are correct that the taskbar icon is an application icon - it isn't changed by an individual form even if that is assigned its own form icon.
Having said that Taskbar behaviour will depend on your Access version, OS & your own settings.
I only rarely use A2003 these days so my memory is a bit hazy
IIRC, Access 2003 will show separate taskbar icons for each type of open object (form/table/report etc) in WindowsXP

Your user description says Access 2003, WindowsXP but the screenshot shows an A2016 icon

How do you know that the taskbar icon goes blank before the load event occurs?
Do you mean its blank when the first break point occurs?

Is you main menu form acting as a 'switchboard' or does it load a very large data table (which may take some time)

Lets try some more systematic tests in turn until the cause becomes clear:
a) Restore the normal startup but disable the form load event. Is it OK now?
If yes, the issue is somewhere in your form load event.
If so, you may have form corruption. Make a backup then DECOMPILE then RECOMPILE & finally COMPACT. Restart and see what happens

b) If still a problem, re-enable the form load event but disable all the code in that event except the final line or section of code.
Is it OK now? If Yes, re-enable another section of code. Rinse & repeat until the issue recurs

c) If still a problem, create a new hidden startup form. In its form load event, add code to open your current form then close the new startup form

d) Finally how large a file (kb) is the eagle application icon? If its large maybe its taking some time to load?
Temporarily remove your eagle app icon so it just uses the Access icon in the taskbar. Now what happens

Hope at least some of that helps. I'm afraid problems like this can be tedious to solve!

[maxis]

Upfront, THANK YOU for your help and time with this. Your ideas were a new set of eyes.
As you puzzled out, it happens before the first LOAD EVENT because the first line of the LOAD EVENT is a msgbox which display after the BLANK SCREEN has comes up. There are no large files in this database. The whole database is only 4mg in size, but never more than 200 lines in any one table.

a) nothing here, but we did a decompile / recompile already from past issues
b & c) we just called a different form and NO BLANK SCREEN - by using your eliminate the FORM factor it appears SOMETHING is happening in the FORM - obviously not something obvious, but now we have a DIRECTION to go thanks to your input
d) size just isn't a factor on this database

Yes, it can be tedious to solve, but your input and suggestions did eliminate that it's very likely something in the form. NOW the hard work begins AGAIN. Thank you ISLADOGS!

[isladogs]

You're welcome. Tempting to stick with solution c) if that 'solves' the problem