Database Replica, Copy, Back End, Wah?

[kballing]

I have just finished putting together a database for a lab inventory. I've got all the modules, forms, relationships, etc. just how I want them. Now I'm wondering what is the best way to deploy this. The database links to some existing tables that I have no control over and also uses some new ones.
I am at one site and the majority of end users are at another site running anything from access 97 to 2007 so there will be some bugs to work out in the code.There will typically only be one user accessing the DB at a time.

The problem with this database's predecessor (not my doing) was that some of the users were making copies of the data in all sorts of places and modifying the forms to suit their specific desires which lead to loss of data integrity. What I want is a copy that only I as the developer can access (in a private folder) and get the bugs out of while the users make due with the current state of things untill I roll out another version. I only want the users to see the essential forms, queries, etc.
I'm a DB novice and I've read a bit about diffent ways of doing this, but remain confused as to which method is best. Do I want a replica? Can't I just have a backend DB with my original tables there, and then create a front end database for my forms and queries, then copy the front end to the user's directory? Is it that simple?

I know that this isn't the best post, but I'll be watching it and can give input as needed.

 

[SOS]

Yes, you have a backend database where you link a FRONTEND to and then give each user a copy of that frontend. You can secure it by removing the USE ACCESS SPECIAL KEYS in the startup options so they can't use F11 to get to the database window and then you can do a search here for the Disable Bypass Key code which will keep them from holding shift to get to the database window/or nav pane when opening the database.

Also, you can look into some frontend auto upaters that exist to help you manage their frontends and keep them up to date.

Bob Larson has a free tool which will enable auto updating of any frontend and Tony Toews has a frontend auto updater.

 

[SOS]

and NO you do not want to use replication in this situation.

 

[kballing]

Programming and DB management is not in my job description, I just got handed some projects that our house programmer didn't have time for. All of her databases are set up as replicas and I have no clue why. It's nice to hear I understood this correctly and to confirm that my coworker is smoking crack.

 

[SOS]

If set up as replicas, I hope that is only the backend (tables only) because if it isn't then they are playing Russian Roulette with their database as it is HIGHLY likely that something will happen to corrupt everything. Replication should not be used for frontend objects and definitely does NOT need to be used in most circumstances if the people are connected by a LAN.

 

[dfenton]

Replication cannot even be used for data if it's a mix of A97 and later versions, since a replicated data file is editable only in a version of Access that is matched to the Jet version of the replica. That is, a Jet 3.5 replica is editable in Access 97, but not in any later version.

Sounds like a situation where Terminal Server would be a good solution, or Sharepoint.