 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
MS Access Forum / Multiuser / Networking / August 2003Holding constants in a multi-user environment.
I am holding some processing constants in a one entry table but this causes problems when other users are involved as they share the same constants. Could someone please direct me to some help. Do I need to identify each user and keep separate entries in the table for each user? I am not very good at VBA and survive on macros. Thanks, Chris - Canberra, Australia. > I am holding some processing constants in a one entry table but this causes > problems when other users are involved as they share the same constants. [quoted text clipped - 5 lines] > > Chris - Canberra, Australia. > I am holding some processing constants in a one entry table but this causes > problems when other users are involved as they share the same constants. > Could someone please direct me to some help. Do I need to identify each > user and keep separate entries in the table for each user? I am not very > good at VBA and survive on macros. Multi-User apps should be split with a shared data file and each user having their own local copy of the front end file. Then these kinds of tables can be placed in the front end where they don't interfere with each other. A shared table with a row per-user would work also, but there are many other reasons why a split app is better. Thanks Rick. So obvious! Does the splitting wizard allow a table to be left in the front-end? Chris. > > I am holding some processing constants in a one entry table but this causes > > problems when other users are involved as they share the same constants. [quoted text clipped - 7 lines] > table with a row per-user would work also, but there are many other reasons why > a split app is better. Rick, Don't bother answering it is all working OK. Thanks again. Chris. > > I am holding some processing constants in a one entry table but this causes > > problems when other users are involved as they share the same constants. [quoted text clipped - 7 lines] > table with a row per-user would work also, but there are many other reasons why > a split app is better. |
Reply to this Message |
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2008 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.