Keeping a Form Maximized

I'm working in Access 2007 for a project which will run in Access 2003.

A popup style dashboard form opens another form whose onLoad event executes 'doCmd.Maximize'.
To prevent users from restoring or minimizing the form, its control box (and avery other such control) is set to NO.

I'm just curious.  When I return to the dashboard after hiding the maximized form (Me.Visable = False), and subsiquently return to the hidden form, setting 'Form!myForm.Visable = True' from a dashboard command button, the form appears, but restored not maximized.

In fact, it looks like any time I switch program focus to a non-maximized form, returning to the form I want maximized finds that form's size not only 'restored' but also unable to be maximized, even interactively by double-clicking the titleBar.  At what trigger event will 'doCmd.Maximize' always "re-maximize" my form?  I've tried onLoad, onOpen, onCurrent.  

. . .and why is it so difficult to search MSDN.com for answers?!
Greg-CAsked:
Who is Participating?
 
dannywarehamConnect With a Mentor Commented:
Add the docmd.maximise to the On_Focus of your form.
Whenever your form is being used, it will maximise.

>>. . .and why is it so difficult to search MSDN.com for answers?!
There are sooooo many answers in there, it can be difficult withour a specific search quey term.
:-(
0
 
dannywarehamCommented:
Sorry - just reread your question.
Why does it do it? There's probably a windows default setting that has all applications window sizes as "restore".
It's a known bug:

http://www.mvps.org/access/bugs/bugs0026.htm
0
 
Jeffrey CoachmanConnect With a Mentor MIS LiasonCommented:
Greg-C,

I also know that a lot of new "Window" properties and modes are now available in Access 2007.
Further complicates things.

Also you must be *very* careful if you are developing in 2007 for an app that will run in Access 2003.
Make sure you do not save the database into the 2007 format.

Also make sure you do not touch any of the "2007 specific" properties.
As they can cause strange behavior in Access 2003.

Some things you will get warned about, like Attachment fields, other things like Split forms and "Alternate Back color" will not say a word.

I have had lots of databases that were worked on in 2007, (even though they were still in the 2003 format) crash or lock up on me for no reason.

So be careful.

JeffCoachman
0
Cloud Class® Course: Microsoft Exchange Server

The MCTS: Microsoft Exchange Server 2010 certification validates your skills in supporting the maintenance and administration of the Exchange servers in an enterprise environment. Learn everything you need to know with this course.

 
dannywarehamCommented:
Great advice Jeff.
Also, different Access versions refer to different MS Office locations on your PC for their support files (references).
It's a pretty big no no to develop in a different environment than the user.
Even if you convert your db to 2003, it may still stop working because of broken references in your VBA.
0
 
Jeffrey CoachmanMIS LiasonCommented:
Greg-C,

Can you post a sanitized version of your DB here, along with detailed instructions on how to re-create this issue?

JeffCoachman
0
 
Greg-CAuthor Commented:
I want to close out this question.  Your answers were helpful but I couldn't get the 'onFocus' option to work.  I've been busy with other things and will revisit this later.  Thanks for the good advice about version conflict caution.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.