I want people w/ 2000 and 97 to both be able to use the database, and record their info to a single set of tables, with 2 or more concurrent users. I am very concerned that a 2000 user would accidentally convert the 97 db into 2000; and I can't find a way to prevent conversion without modifying the registry on each PC. Overview - simple Access 97 db structure where users load info into one main table using a loading macro. Then they view data in simple forms and run comparison queries against another main table loaded by automated process, a few ancilliary tables with infrequent updates managed by administrator.
So, I plan to split a 97 database into 97 BE and 2 FE versions 97 and 2000. The 97 BE will live on a shared file server on a WAN.
MY QUESTION: Can I just put the 2 front end versions on my LAN and let my users hit the db in that shared directory, or do I really need to have each user copy the appropriate FE version onto their local PC?
If I have them load a local copy of the FE onto their PC wouldn't I have to reload the db every time I upgrade the original or add features to the forms? That sounds like a versioning nightmare. But if that is the safest way to support a multi-user environment, should I do the local version anyway?
Thanks,
Eric
So, I plan to split a 97 database into 97 BE and 2 FE versions 97 and 2000. The 97 BE will live on a shared file server on a WAN.
MY QUESTION: Can I just put the 2 front end versions on my LAN and let my users hit the db in that shared directory, or do I really need to have each user copy the appropriate FE version onto their local PC?
If I have them load a local copy of the FE onto their PC wouldn't I have to reload the db every time I upgrade the original or add features to the forms? That sounds like a versioning nightmare. But if that is the safest way to support a multi-user environment, should I do the local version anyway?
Thanks,
Eric