corruption question

[rjoshi2]

I am setting up a database that will be used by multiple users across a network. They will only be allowed to see and manipulate data that they entered. I have also set up the database to using user-level security (workgroups). My question is do I need to set up a different front end for each user to prevent possible corruption of the database. Any advice would be appreciated.

Thank You,
rjoshi2

 

[KenReay]

Hi

Well you do not have to, but it generally recommended as the way to do it, ie have the backend on the server, and a front end on each client PC. To minimise the workload of course you should have a single copy of the FE (with backups of course!!) on which you do the maintenance/enhancement work, and distribute this to users when tested etc Regards

Ken Reay
Freelance Solutions Developer
Boldon Information Systems Ltd
Website needs upgrading, but for now -

http://www.kenneth.reay.btinternet.co.uk

UK

 

[rjoshi2]

If I set up a FE for each user won't I have to set up the user-level security for each user? Is there a way around doing this?

Thank You,
rjoshi2

 

[beetee]

As another poster put it, you MUST read the security FAQ until you understand it.

Regarding users, you can associate users with groups and set group permissions

 

[rjoshi2]

Is this a reasonable solution to prevent me from having to set up user-level security for each user and prevent the database from being corrupted?

Use UNC to link the FE and BE. Place a copy of the FE in the C directory for each user. Then create a shortcut for each user that point to their copy of FE. The shortcut would also point to the workgroup file database on the network. Can you use UNC when point to a file on the network for a shortcut.

Shortcut info
"C:\Program Files\Microsoft Office\Office10\MSACCESS.EXE" "C:\FY 03 Comt Register.mdb" /WRKGRP "O:\Commit Register - OBAM\Secured.mdw"

Any help would be appreciated.

Thank You,
rjoshi2

 

[beetee]

That's pretty much precisely what I do.

Your shortcut should look more like:
C:\Program Files\Microsoft Office\Office10\MSACCESS.EXE" "C:\FY 03 Comt Register.mdb" /WRKGRP "\\UncName\Commit Register - OBAM\Secured.mdw"

Additionally, you will want to make sure that any linked tables you use are linked using UNC's.

You may find it useful to write some VBA code to perform the linking automatically (e.g. look for the name of the workgroup [print dbengine.SystemDB]) and use it's path part to find the name of the back end db.

VB help has some good sample code of how to work with tabledef objects and thus to set the connect property so you can perform linking programatically.

HTH

 

[annsolomon]

Somebody, PLEASE tell me what UNC means.

rjoshi2, I use the same methodology mentioned here (be/fe with a shortcut that puts the user into the appropriate workgroup) but I don't do it so much for "preventing" corruption. It may help reduce the possibility but I don't know of anyway to prevent the possibility of corruption. My main reason for doing it this way is speed (less activity between server and user PC) and to keep users from tripping over one another while using the same forms, etc.

On a side note, I learned from another thread how to create a batch file that I'll put on my users' PCs that will compare the version of the fe on the server to the version of the fe on the local PC and, if different, will copy the newer version to the local PC. The file then launches the application. It's double-cool and is going to save me loads of time now that I won't have to physically go to everyone's PC everytime I have a new fe. One little problem not yet figured out is that that batch file (command window) shows up in the top portion of the screen and forces the my application to the bottom half of the screen. I'm still trying to find a way to run the batch file minimized and my application full-screen. Regardless, it's a sweet deal and I intend to go forward with it. If you're interested, the instructions I followed can be found in the Developer's Section at:

http://www.alphabetcitydataworks.com/

Ann

 

[KenReay]

Hi

UNC

Universal Naming Convention

(I think)

it just means the \\servername\sharename\foldername\filename style of giving a filespec instead of the mapped drive method F:\foldername\filename

Hope that helps Regards

Ken Reay
Freelance Solutions Developer
Boldon Information Systems Ltd
Website needs upgrading, but for now -

http://www.kenneth.reay.btinternet.co.uk

UK

 

[annsolomon]

Hi Ken. Ya know I think I did hear that about a hundred years ago when I took a Netware Administrator's class. Never got to use what I learned and obviously am losing the knowledge.

Thanks! Ann

 

[KenReay]

Hi ann

Well I am a dinasaur from the Mainframe then Mini Computer then Netware days (even including MsDos!), so I vaguely remember such things Regards

Ken Reay
Freelance Solutions Developer
Boldon Information Systems Ltd
Website needs upgrading, but for now -

http://www.kenneth.reay.btinternet.co.uk

UK