Splitting and security

[Gina]

Hi All!

I have a couple really stupid questions:

I have a database that I created on my home computer; I
now want to install it on my office fileserver (to be used
by about 20 people). I want to split the db into a
front/back end, and establish passwords for users.

Can I try to do the splitting and security on my home
computer, and then transfer the front end, back end, and
secured.mdw files to the fileserver and individual
computers, or should I do all the security once I've
installed the back end on the fileserver? Also, where is
the secured.mdw file stored (ideally)? (On the
fileserver?)

Thanks for any suggestions (and excuse my ignorance)...

Gina

 

[Scott McDaniel]

You can split your db and apply security from your home system, then
transfer everything (frontend, backend, and .mdw file) to your office
environment. You can either place the .mdw file on your server or on the
desktop. Set your shortcut paths to it like this:

"Path to MSAccess.exe" "Path to your database" /wrkgrp "Path to your .mdw
file"

Of course, if you put the .mdw file on each desktop you will have to
sychronize each .mdw file every time you make a change to it. However, there
have been some recent postings regarding corruption in the .mdw file when
placed on the server, so this may be better strategy in the long run.
Regardless of what you do, however, do it on a COPY of your database until
you are sure everything is working correctly. Before even attempting
security, download and read-read-read the MS Access Security FAQ:

http://support.microsoft.com/default.aspx?scid=/support/access/content/secfaq.asp

 

[Gina]

Thanks for the advice! (And I'll be sure to read the MS
Access Security FAQ.)

Gina

-----Original Message-----
You can split your db and apply security from your home system, then
transfer everything (frontend, backend, and .mdw file) to your office
environment. You can either place the .mdw file on your server or on the
desktop. Set your shortcut paths to it like this:

"Path to MSAccess.exe" "Path to your

database" /wrkgrp "Path to your .mdw

 

[Guest]

On thing that I learned (and I am sure you already came to this same conclusion) is that you should remember to use the Link Manager on the Front End when you put it on the PCs back at the office. I had the hardest time with this, but it's because our IS department doesn't install all the wizards when they put MS Access on our PCs. Once they put it on by request, Link Manager worked like a charm.

----- Gina wrote: ----

Thanks for the advice! (And I'll be sure to read the MS
Access Security FAQ.

Gin

-----Original Message----
You can split your db and apply security from your home system, the
transfer everything (frontend, backend, and .mdw file) to your offic
environment. You can either place the .mdw file on your server or on th
desktop. Set your shortcut paths to it like this

database" /wrkgrp "Path to your .md

file

Of course, if you put the .mdw file on each desktop you

will have t
sychronize each .mdw file every time you make a change to it. However, ther
have been some recent postings regarding corruption in the .mdw file whe
placed on the server, so this may be better strategy in the long run
Regardless of what you do, however, do it on a COPY of your database unti
you are sure everything is working correctly. Before even attemptin
security, download and read-read-read the MS Access Security FAQ

http://support.microsoft.com/default.aspx

scid=/support/access/content/secfaq.as