Steve: You shouldn't have everyone using the same RBase.cfg file. You should edit each workstation's cfg file to put a distinct value in the NAME option. That message of "the user name is already active" means that you are replacing another user's session with the current one. This is the way it was designed, so that if a user unexpectedly aborted their connection it would be "cleaned up" the next time that same person came back in. At this point you have everyone as being the "same person"!
My experience is that the first user to log in with that name will eventually lose their connection to the database. Each successive RBase user will kick off the previous one. Really important that you get to those .cfg files and put in unique names! Karen > Somewhere in this "SET EOF OFF" solution may exist an answer for one of my > problems. > > Using 4.5++, the original set up was a single person operation. I don't > believe that we had these problems back then. Recently a server was > installed and others are now accessing RBase from the server. The only thing > I did was "set multi on" and no granting of rights is necessary (everyone > has all rights). I simply placed an icon on each screen and all RBase > operations were on the server. The same RBASE.CFG is used by all. The > operating system is XP. > > The problems do not seem to happen predictably. There is no actual login > and a screen notice is presented "The SERVER.SYS file shows the user name > [EPU1]as already active." when a second user in on the system. We always > hit <ENTER> to continue. > > Problems: > > 1) If a client machine, with RBase active, remains out of use for more than > a minute or two the system kicks the user off on a single key stroke (screen > goes blue and to R> prompt). Sometimes a complete reset of all systems seems > to resolve issues. The actual time here may be moot since the trigger may be > caused by activity on the other machines. I wonder if this is a SERVER.SYS > situation. > > 2) When printing an invoice, or when doing a look up, occasionally the > client machine seems to hang up and the operation is so incredibly slow. > Can this be a SET EOF OFF remedy? We have been watching the task manager to > see if something is clogging the system but do not see a pattern yet. > > So far, the program has been tested on two other single user systems and > neither problem has ever showed up. > > Thoughts appreciated > > Steve Ambrosini > > > -----Origina
