Creating the program

[deville75]

I have a database made in MS Access. It has forms that allow the user to do certain things, such as add to the database, and so on. I only want the user to be able to run a program that will run the one, main form i've created it (as well as any other form that the main for lnks to). how do I do this?

 

[Fifty2One]

tools, startup, display forms/page
click down and find your main menu, this will open your main menu form on start up of your application.
if you dont have a main menu then create the form in forms - new - design view and populate it with command buttons to make a slick push button controlled database.

 

[deville75]

tools, startup, display forms/page
click down and find your main menu, this will open your main menu form on start up of your application.
if you dont have a main menu then create the form in forms - new - design view and populate it with command buttons to make a slick push button controlled database.

Ok this is cool, but I don't want the user to have access to the tables. This just means every time I open the database workspace it starts up with my main form. I want a completly seperate program that only opens that form. I don't want the user to go and open my MS Access database. I'm not sure if I'm explaining this correctly.

 

[KeithG]

If you want a seperate program you will need to use something like Visula Basic 6.

 

[neileg]

Perhaps you need to implement Access Security, or maybe roll your own.

Perhaps what you need is a split datatbase. This works by having the data tables in the back end (BE) and the forms etc in the front end (FE). In reality, these are both Access databases but they are linked. It is possible to view the linked tables in the front end, but there's lots you can do to hide this from the users so their only way in is thorugh your forms.

Try searching these forums for 'security' for lots more help.

 

[Dennisk]

if you look at the startup parameters you will notice a check box to hide the database window. also individual tables, queries etc may be hidden.

 

[deville75]

if you look at the startup parameters you will notice a check box to hide the database window. also individual tables, queries etc may be hidden.

OMG... I did that, but now I'm screwed! I unchecked everything and now I can't access any of the database windows for my own editing purposes. How do I change the startup? The tools menu option is missing now.

 

[KeithG]

Hold down Shift while opening the database.

 

[deville75]

lol, wow I'm such a newb.. thx

 

[deville75]

Ok there is this feature for User-Level Security, which allows me to create users. I think this should work, but the wizard is very unclear. But this is basically what I want. I'll see if I can figure it out to get it working properly.

 

[Dennisk]

all objects can be hidden and to unhide then goto Tools/Options/General and check hidden objects.
In addition to unhide the database window goto Window/Hide/UnHide

 

[deville75]

OMG MS Access is really getting me angry now. I've applied USer-Level Security now and it totally messed things up. It won't let me edit anything even when I login as admin. How do I get rid of the security now?

 

[deville75]

It seems like it's applied the security to all MS access databases

 

[Dennisk]

I think what you have done is to apply security to your system.mdw which is the default workgroup. When you create a workgroup be sure to create a new .mdw for each application.

Now you need to obtain a 'clean' .mdw. normally I keep a copy 'just in case' I screw up the default - which I have done so you are not alone.

If you restore Access it will create a 'clean' system.mdw for you, however keep the existing .mdw by renaming as you still might need it to gain access to your database.

A fellow developer told me yesterday that if you keep copying an Access 97 database onto DIFFERENT DRIVES eventually you may be able to open the db without a workgroup. Or when you have restored access create a blank db, then join your workgroup open the problem database and export each table/query/form to the blank non-workgroup protected db.

 

[NonAccessGuru]

Along this same line (I hope), I'm mailing a CD about 700 miles away to a user that will be using my database on a single home PC (no network). As files, there will be the .mdb DB and a new workgroup file (in the same folder as the DB) I created called "system2.mdw" with admin and users appropriate permissions. The recipient of the DB already has Access on their system so they have the default "system.mdw" file on their system.

When they copy my DB onto their HD along with the "system2.mdw" workgroup file in the same folder and run the DB will my DB look first for my "system2.mdw" workgroup file and ignore the default "system.mdw" on their system (thus retaining the security my "system2.mdw" file contains)?

There's been mention of necessary REGISTRY entries for the "system.mdw". When my DB is first run on their system will it make a registry entry by default referencing my "System2.mdw" workgroup file and not their default "system.mdw"? Or does this registry entry have to be manually entered in the registry?

My concern is there may no longer be a username and password login on their system if my DB looks to their system.mdw file first (which contains no security).

Thanks!

Rod

 

[Dennisk]

To run a workgroup protected db use a shortcut eg

"mypathToAccess\access.exe" "mypathTotheDatabase\myDatabase.mdb" /WRKGRP "mypathToTheWorkgroup\myWorkgroup.mdw"

Access logs you on the workgroup when you open the db and logs you off from the workgroup so next time you use access you are using the default system.mdw