Replication ***PLEASE HELP***

[Guest]

We have created a secured database. We replicated the front-end and now our
links are not working. We are getting a Run time error 3027 "can not update
database or object is read only." It occurs when the VB tries to write to the
query. I am logged in with all permissions and still receiving this error.
When I go back to the Design Master all of the links work. Please help we are
presenting this to our management staff tomorrow!!!

 

[TC]

Not what you want to hear at this point, but: replication is a complex
topic, and replicating a secured database is even more complex! You may
have better luck in microsoft.public.access.replication. If you re-post
your question there, I'd try including a bit more information; eg. the
sql of the query.

Again, not what you'd want to hear, but: it's not a good idea to make
significant changes (like securing or replicating a database) the day
before you're due to demonstrate to management! That is really just
asking for trouble ...

HTH,
TC [MVP Access]

 

[Lynn Trapp]

To add to TC's thoughts, replicating the front-end is NOT a good idea -- it
has been known to cause corruption. Jet Replication is designed for data
only.

--
Lynn Trapp
MS Access MVP
www.ltcomputerdesigns.com
Access Security: www.ltcomputerdesigns.com/Security.htm
Jeff Conrad's Access Junkie List:
http://home.bendbroadband.com/conradsystems/accessjunkie.html

 

[Guest]

What is the best way to have multiple users access the database. we have 18
users with different security levels. This database will be completely housed
internally on our network drive. Do we even need to replicate or can multiple
people use a non-replicated copy?

Thanks

 

[Keith Wilby]

What is the best way to have multiple users access the database. we have
18
users with different security levels. This database will be completely
housed
internally on our network drive. Do we even need to replicate or can
multiple
people use a non-replicated copy?

Replication is intended for multiple users on, for example, separate
laptops. It enables separate users to merge their changed data into one
dataset. What you need is a split database - a back end file on a server
(containing just tables) and a front end on each user's PC (front end
contains all other objects and links to the back end tables). That way, all
of your users are accessing the same dataset.

If you want your users to have different level of access then you need to
set up user-level security. The first step is to read the MS FAQ (link on
my web site). DON'T attempt to apply ULS to your main app until you are
confident of getting it right - work on a copy, the loss of which would not
embarrass you - it is very easy to lock yourself out.

HTH - Keith.
www.keithwilby.com

 

[TC]

Further to what the others have said: you are talking about a
"multi-user" database. Access can do that fine. But amongst other
things, you'll have to split your database into a so-called "front
end/back end" (FE/BE) structure. Google the Access groups for those
terms, you'll find lots more information on what that is, & why you
will need it.

HTH,
TC [MVP Access]