Security-Workgroup Confusion

[Pattyt]

Hello,
I am in the process of developing a db that will have user-level security
and that will be split into FE & BE. My boss wants to implement a copy of
this db in another physically separated site. Both db’s must have the same
format but must be physically separated, meaning that each center will have
their own db and will not share information with each other. My question is
in regards to the workgroup file, I would like to have just one workgroup
file with both sites user-information. Can I create the workgroup through
the first db, then create a shortcut for this file and place it on all users’
desktop (including those users from the 2nd db)? Or would I have to create a
separate workgroup file for each db?

If it helps, both sites share one common shared-network drive which is where
I will be placing the workgroup and BE of both db’s.

 

[Joan Wild]

Hello,
I am in the process of developing a db that will have user-level security
and that will be split into FE & BE. My boss wants to implement a copy of
this db in another physically separated site. Both db's must have the
same
format but must be physically separated, meaning that each center will
have
their own db and will not share information with each other.

Or would I have to create a
separate workgroup file for each db?

You can use a single workgroup file.

If it helps, both sites share one common shared-network drive which is
where
I will be placing the workgroup and BE of both db's.

Do you mean that each site has a server, or do you mean that both sites
share the same server. If the latter, you'll want to reconsider. Access
run directly over a WAN is not going to work. You'll want to consider using
Terminal Server. See http://www.members.shaw.ca/AlbertKallal/Wan/Wans.html

If each site has their own server, then you don't need to worry about this.

 

[Pattyt]

Thank you for your help Joan,
In response to your question, both sites are part of the same server.

Another quick question:
Would it be safe to create the first DB and once complete make a copy of it
and re-format it to fit the second site needs (logos, pictures, etc). And
then continue with security and splitting? Or should I create each one from
scratch?

 

[TC]

Your only issue with having seperate workgroup files is the need to
keep them up-to-date with any changes.

Of course, you have the same issue with the FE files - keeping them up
to date with any changes.

HTH,
TC

 

[Joan Wild]

Thank you for your help Joan,
In response to your question, both sites are part of the same server.

Did you read Albert's page on using Access over a WAN? It isn't adviseable.

Another quick question:
Would it be safe to create the first DB and once complete make a copy of
it
and re-format it to fit the second site needs (logos, pictures, etc). And
then continue with security and splitting? Or should I create each one
from
scratch?

I would go ahead with one db; split it and secure it. Then make a copy of
it and make the changes specific to the second site.

 

[Pattyt]

The second site is part of the same server that the first site has and they
connect via VPN. This would work correct?

 

[Joan Wild]

The second site is part of the same server that the first site has and
they
connect via VPN. This would work correct?

I believe Albert's article addresses this. Yes it will *work*, but it will
be slow and you are pretty much guaranteed to corrupt the database.