469,364 Members | 2,332 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 469,364 developers. It's quick & easy.

ACCESS 2000 Full Screen and Command Buttons Removed

16
Greetings;
For a project, I need to design the DB to show full screen and remove the command buttons across the top... I recall F11 will show the command buttons was removed, but need to know how to satisfy the two issues I have...

Thank you,
Steve
Feb 9 '07 #1
6 3361
nico5038
3,080 Expert 2GB
In the Tools/Options menu you can disable the menubars and function keys.
Just make sure you keep control.
Pressing SHIFT when opening the .mdb will pass the startup process and allow access to the database window when not disabled...

Nic;o)
Feb 9 '07 #2
ADezii
8,800 Expert 8TB
Greetings;
For a project, I need to design the DB to show full screen and remove the command buttons across the top... I recall F11 will show the command buttons was removed, but need to know how to satisfy the two issues I have...

Thank you,
Steve
Tools ==> StartUp then deselect Menu and/or Toolbar Options. To disable Function Keys, you must click on the Advanced>> button in the StartUp Dialog.
Feb 9 '07 #3
missinglinq
3,532 Expert 2GB
I think you're also asking how to have your form display full screen, am I correct? You simply have to play around sizing it until you get it to over the screen! This will take a little bit of diddling, but it does create a nice Visual Basic like program effect. I use it frequently, as I find that non-power users (my end users are mainly medical professionals) are intimidated by the Access environment. Rather than having to go roaming thru the various pulldown menus looking for a task they need to perform, I provide them with custom buttons for just those functions they need.

The only caveat to using full screen forms is that sooner or later some user (maybe even yourself) will buy a new machine, and its default Screen Resolution will be higher than the one you developed your db on. This will, in effect, "shrink" your form so that it's not "full screen" anymore. The answer to this is an custom function to "resize" the screen to match the new resolution. Fortunately, someone has already done the work for you! Go to this site and scroll down to the "Access Form Resizer" and download it. I've used it before without problems, and best of all, it's FREE!

http://jamiessoftware.tk/resizeform/afr.exe
Feb 9 '07 #4
NeoPa
32,185 Expert Mod 16PB
If your requirements aren't so demanding though, a simple DoCmd.Maximize (DoCmd.Restore to revert) should maximise the form for you.
Feb 10 '07 #5
steve i
16
Thanks for all the information...that is exactly what I need todo...si


I think you're also asking how to have your form display full screen, am I correct? You simply have to play around sizing it until you get it to over the screen! This will take a little bit of diddling, but it does create a nice Visual Basic like program effect. I use it frequently, as I find that non-power users (my end users are mainly medical professionals) are intimidated by the Access environment. Rather than having to go roaming thru the various pulldown menus looking for a task they need to perform, I provide them with custom buttons for just those functions they need.

The only caveat to using full screen forms is that sooner or later some user (maybe even yourself) will buy a new machine, and its default Screen Resolution will be higher than the one you developed your db on. This will, in effect, "shrink" your form so that it's not "full screen" anymore. The answer to this is an custom function to "resize" the screen to match the new resolution. Fortunately, someone has already done the work for you! Go to this site and scroll down to the "Access Form Resizer" and download it. I've used it before without problems, and best of all, it's FREE!

http://jamiessoftware.tk/resizeform/afr.exe
Feb 14 '07 #6
NeoPa
32,185 Expert Mod 16PB
Thanks for all the information...that is exactly what I need to do...si
Thanks for letting us know. Glad Linq was able to help you :)
Feb 14 '07 #7

Post your reply

Sign in to post your reply or Sign up for a free account.

Similar topics

6 posts views Thread by Peter Frost | last post: by
1 post views Thread by linuxnooby | last post: by
27 posts views Thread by Wayne | last post: by
5 posts views Thread by King | last post: by
9 posts views Thread by prakashwadhwani | last post: by
1 post views Thread by CARIGAR | last post: by
reply views Thread by suresh191 | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.