Newbie to Access...

[rhoneyfi]

Hello all,
I have created a simple database that has a data input form. How do I do the following:
1) When the user opens up the database, the form automatically opens
2) How can I prevent any users from going into 'design mode' and modifying the database.....but occassionally I may want to go into design mode to make changes...

I know these are basic questions...but they are useful ones

 

[psemianonymous]

1. Go to Tools->Startup and there is an option for what form to start up with (as well as a lot of other useful options)
2. This is a common question, with a difficult answer to swallow: there is no good way to prevent your users from messing with your database. There are several levels of security, choose whichever suits your needs:

-Uncrackable security - impossible with MS Access (though using compiled .MDE files fully secures your code/forms/queries)
-Difficult to crack security - you must use the built-in-security features that come with Access. This is not an easy task. Google for the "MS Access Security FAQ" for a copy of the MSKB article.
-Casual security - i.e. prevent accidental intrusions to the database - I think this is what you're after.


For the third, I'd say that removing the database window (another startup option) should be good enough to prevent your users from messing with the database. Of course, it all depends on the users. The next step up is a difficult one to get right (the step to built-in security) - I don't want to scare you, but just know that it's not as designed for ease-of-use as it should be.

--
Find common answers using Google Groups:

http://groups.google.com/groups?group=comp.databases.ms-access

Corrupt MDBs FAQ

http://www.granite.ab.ca/access/corruptmdbs.htm

 

[gnealw]

Hey there....I am fairly new myself but I can help with your first question. With your database open, go to Tools, then Start up. There will be display options there. You probably want to "uncheck" the Display Database window and Display Status bar boxes. After that, if you want to get to the Database window, hit the F11 key.

I know you can keep the database "read only" for your users, but I would have to look that one up myself!

 

[GDGarth]

The first question is really easy:

Go to "Tools", "Startup" and put your form name in the box that says "Display Form". The next time you open the database, it will open up the form automatically.

The other issue is a bit trickier - but it's definitely something you need to do. You need to implement Access security. To implement security, you need to follow all the steps correctly.

There's a security FAQ that should lay it out pretty well for you. The basic steps are:

1. Create a new workgroup using WRKGADM.EXE. Don't just make a copy of System.mdw.

2. Join the new workgroup.

3. Create a new user name for yourself, and set a password for your user name. Put your user name into the "Admins" group.

4. Remove the default "admin" user from the "Admins" group (leave them in the "users" group).

5. Open your database and run the User Level Security Wizard. This will make a secure copy of your database without changing the original.

6. Open the new, secure database, and set up your user and group accounts. If you don't want the default user to have access to your database, set up a new user group, and remove all permissions from the existing user group.

This is the condensed version of Access Security. I recommend you read the instructions so you understand it before you implement it.

 

[rhoneyfi]

Thanks for the great advice.
The "tool--> start up' option is just what I want. I have my form automatically loads and none of the menus show. Now, lets say down the road, I want to modify the database a bit...how do I bring back all of the menus?

 

[gnealw]

Just hit the F11 key

 

[psemianonymous]

Yeah, this is the "casual" part of "casual security". To disable ALL special startup options, hold down SHIFT when opening the database and it will open the database "as normal". This becomes especially important if you disable toolbars, menus, etc.


And as gnealw posted above, you can always recover the database window by hitting the F11 key. So you see this solution isn't very rock-solid.

--
Find common answers using Google Groups:

http://groups.google.com/groups?group=comp.databases.ms-access

Corrupt MDBs FAQ

http://www.granite.ab.ca/access/corruptmdbs.htm

 

[rhoneyfi]

Thanks for all your help everyone....My database is all set up and ready to rock and roll !

 

[tj63069]

Hi
Newbie too but I can tell you that hiding everything in the start up will be easy to crack for a user that notices that there's a "Databse Window" Icon in the tool bars. You must Uncheck all of the Toolbar options and Allow full menu. The users will still be able to print in Access 2000 until they discover the shift key and somebody will. Hence Casual Security. I am not sure if you can still print in earlier versions???????

 

[uscitizen]

hi -

i'm at the point where tightening the hatches isn't satisfied by just implementing a database password everyone needs to use or hiding all the tables, reports, etc etc i've developed from the user and giving him/her just a switchboard they can see. the high command have expressed an interest in seeing the user community is prevented from making changes to the underlying design of the db. hence i've been trying to fine some useful pubs that'll help get me started on my way. i'm approaching all this w/ some trepidation inasmuch as what i'm reading is not quite 100% transparently clear to me. for example, high command is interested in seeing the currently un-secured databases written in either ms Access '97 or 2000 stored on a central server which users will access from their local pcs. i have been reading about mdw files and the security wizard and running the Wrgadme.exe program in lieu of using the aforesaid security wizard and workgroup information file and frankly i'm glad it's five o'clock because i'm going to work on this tomorrow.

 

[jbleoo]

Hi Your first question is easy! but the security is allitle more advanced.

In the menu bar select TOOLS then STARTUP a form will open up in the top right corner there will be a display form combo box. Select the form you want to open and your done.

Now you can stop the mid level user by creating a macro called autoexec.

this will run before anything else....

in the macro have this macro open the mainmenu (Or any other form) in the properties set the form to open in Dialog mode

this will diable things such as F11 key and will disable the menu's that allow you to open the form in desigh mode.

Have fun

 

[psemianonymous]

Basically uscitizen, you need to read up and implement full MS Access/JET security on your databases. The MS Access Security FAQ is out there ... somewhere on the web. It's extremely comprehensive (they should have called it a manual instead of a FAQ).

With Access security, you can make sure no one has access to edit forms except for you, and that's just one of the many great things you can do.

--
Find common answers using Google Groups:

http://groups.google.com/groups?group=comp.databases.ms-access

Corrupt MDBs FAQ

http://www.granite.ab.ca/access/corruptmdbs.htm

 

[uscitizen]

my situation has me running ms access 2000 installed on my local pc. there are currently three communities which are going to use databases i created. the databases will be loaded on a shared server/network drive -- two were written for ms access 97 and one for ms access 2000 because two communities utilize 97 and one utilizes 2000 on their desktops. currently 'security' consists of each database's having been set with a password. period. however it should be kicked up to include usernames and privs and so forth. i have the ms access FAQ document (10/2000) but i'm wondering if what it has to say is premised on the idea that the access installation is loaded on the same platform as the databases themselves. any insights?

 

[psemianonymous]

You'll be fine. Just make sure you create your workgroup information file (WIF for short) in Access 97 format (Jet 3.5 I believe). The WIF is basically a database itself, so make sure it is stored in the "old" 97 format instead of the "new" 2000 format, so that both 97 clients and 2000 clients can use it.


I haven't done a 97/2000 dual-front end application myself, but there are others who have done so successfully. I believe you will be fine.

 

[uscitizen]

Let's say that before Santa Claus arrives for Xmas that Access '97 disappears and we've standardized on MS Access 2000......now my situation has me with a networked drive (the 'I' drive) whereat the Access 2000 databases 'live'. I haven't actually taken any action to override the default security configuration that came packaged w/ the 2000 product but I've read a little (enough to be 'dangerous') and got to wondering about the WIF I think I read I needed to create. My hunch is that it'd need to be on the 'I' drive in order for each user's Access 2000's (which is installed on each user's PC as a standalone) need to read it. Am I wrong? If not, then my focus turns to the integrity of the WIF file itself. How do I prevent users from (un)intentionally deleting or otherwise mucking with that file? One thought is to add 'hidden' to its properties but if there's something 'slicker' around I'd like to hear 'bout it?

 

[psemianonymous]

Impossible to prevent deletion of the file--the same way it's impossible to keep your users from deleting your data file (MDB). Sorry.

The best *casual* defense against this is to make sure they never have to actually browse out to the I: themselves--if their shortcut works fine, they'll never know that the WIF exists anyway, right? But there's no guarantee. Backup often (daily).

 

[uscitizen]

Simply doing a little possibility thinking in line with just wanting to make sure that I'm doing as much as can be done.

Thanks for the straight dope.