Making an Access Application

[Guest]

I have my tables, queries, and macros ready to go, and everything works when
I open the first form. How do I make it, so that the user cannot use the
record navigation buttons at the bottom, and not allow them to get to the
database window?

 

[Meindert Manshanden]

You can disable the record navigation in options of the form. Right click
on a blank spot in the formsdesign. Then disable the recordnavigation.

 

[Joseph Meehan]

I have my tables, queries, and macros ready to go, and everything
works when I open the first form. How do I make it, so that the user
cannot use the record navigation buttons at the bottom, and not allow
them to get to the database window?

Meindert told you the quick answer and it may work fine for you, but if
someone is Access knowledgeable they can work around that. User level
security will stop almost anyone.

I suggest you start by reading
http://support.microsoft.com/default.aspx?scid=kb;[LN];207793

Access security is a great feature, but it is, by nature a complex product
with a very steep learning curve. Properly used it offers very safe
versatile protection and control. However a simple mistake can lock
everyone including God out.

Practice on some copies to make sure you know what you are doing.

 

[Allen Browne]

To disable the database window, go to Tools | Startup, and uncheck the box
for:
Display Database Window

If you don't want the user to be able to activate it with F11 or get to the
Debug window with Ctrl+G, uncheck:
Use Access Special Keys

If you want to prevent the user bypassing this with the Shift key,
programmatically set the AllowBypassKey property.

Presumably you have split the database and created an MDE for the front end
so users cannot modify their forms/reports.

If you need more than that, you can use Access security, though that's
overkill for many applications.

Regarding disabling the nav buttons on the form, you can turn off the
NavigationButtons property but the more important question is why. If it's
because you need to run some code before a record is saved/changed, then you
really need to move that code into Form_BeforeUpdate. That's the only way
you can guarantee it runs regardless of how the save occurs (e.g. menu,
keyboard shortcut, menu, closing form, closing Acess, applying a filter,
changing sort order, clicking in a subform, and so on.)

 

[Guest]

Well, thank you all for the help. I'm getting rid of the navigation buttons
because my users aren't too bright and if pushed would throw the application
off. I implented a password for the application, and the user could just use
the nav. buttons to go to a different UserID.