Most people have a main copy that only the developer can get to. The changes are made there. Then it is copied into each person's "Home Directory" or whatever common location that the 8 copies reside for each person. It would probably we worth your while to build a tool or procedure that will automatically copy the source copy out to everyone. To feasibly manage the "change control" you should take request, make your changes and publish (copy to their directories) on a periodic basis. Most people do it quarterly. I work in a very very rapid development environment also and we use to deploy new copies daily. We now have a scheduled job that does it every Friday.
May God bless you beyond your imagination! Lonnie Johnson ProDev, Professional Development of MS Access Databases Visit me at ==> http://www.prodev.us --- On Mon, 8/11/08, luvmymelody <[EMAIL PROTECTED]> wrote: From: luvmymelody <[EMAIL PROTECTED]> Subject: [ms_access] Splitting the Database question To: [email protected] Date: Monday, August 11, 2008, 11:08 AM We are thinking of splitting a database for 8 multiple users. The question is that people ask to change the forms more often than their underwear. (assumption that it is everyday)Anyone have suggestions for maintaining forms installed on multiple users computers? Jim Wagner [Non-text portions of this message have been removed]
