Tom: If your app was designed to be single-user, there's another thing that could mess you up if you move to multiple users in addition to what others have mentioned. Let's say you add a row into a table and want to grab the PK of the row you just entered; in single-user mode you might have used a command like "WHERE COUNT = LAST" ; this won't work because it could grab the row that another user just entered. Instead use "WHERE COUNT = INSERT". Just an FYI, this has bit me a couple times when I run across code that someone else has written!
Karen > We are moving our internal database project from our single user > development machine out to 20 machines and eventually to users not directly > connected > to our LAN. Using Turbo8 compiler because of several other projects that have > been requested. LAN is a mixture of speedy machines and some dogs that will > need to be replaced at some point. Server works very well. We expect numerous > problems based on the “didn’t know I did not know that” paradigm. Our system > works great on a single computer and has required “some” changes as we > start moving to multiple machines. More will be coming. The differences > between > single user vs. multi user becomes very obvious once it does not work > (particularly in demos) and you have to figure it out. Just part of the > learning > process. > > > > Our question (which may seem very basic): Is there a best way to set up > multi-user R:Base on a LAN system? Data is on Drive Y where we can secure > direct > access from inquiring mice. Is it best for the EXE/DLLs to also be on Drive > Y or remain on individual machine’s Drive C to access the Drive Y database. > We have tried both ways and they work. The concern is LAN speed (particularly > for some older computers) and conflicts between tables/temps/views that the > software uses. It seemed having one network based EXE that multiple people > can > access would really effect our LAN speed/memory, while separate EXE/DLLs on > desktops isolate some memory processes and be primarily limited to moving > data. I have no doubt we have a lot to learn about data and logic conflicts > as > we go through this. > > > > I remain amazed at just how much DYI groups like us can do with R:Base with > some time, interest, and willingness to learn. > > >
