I'll work with my IT contact to see if we can share a workstation directory, thanks for the suggestion. Know what, now that you mention it I do sorta remember sessions not disconnecting back in this version. I remember having to find the one person who was kinda holding the count up and having them connect in multi-off mode and that cleared up the ghosts. However, ghosting is not and never has been an issue with this database. I need to have the IT person get into computer management and see if it shows anyone having the database still open even tho no one is connected.
I guess my question is, if the network shows the database is open, and I'm 100% sure that the user exited gracefully (because it was me doing the testing), does that point to a network issue or could it point to a 6.5++ software issue or something embedded in the database itself... Karen -----Original Message----- From: sales <[email protected]> To: RBASE-L Mailing List <[email protected]> Sent: Sun, Oct 12, 2014 9:58 am Subject: [RBASE-L] - Re: Legacy DB network issues One option to rule out their Server/IT would be to share a directory on a workstation. Copy the database there and see if more than one user can connect. I still use 6.5++ , I'm not sure if it's related but I have an issues with sessions not fully disconnecting. Unless all users are disconnected from the database the number of connected users keeps increasing. This morning my database is showing 83 connected users on a 5 user network. The connection issue hasn't caused any problems as of yet and its been going on for a long time. Richard Kahl On 10/12/2014 9:50 AM, Karen Tellef wrote: In all my years doing RBase, this is a first. Client is on 6.5++ windows. They had purchased an upgrade but the money stopped and nothing was ever converted up. The database autochecks okay, no issues running. However, as soon as one person connects to the database, no one else can connect. They can get out of RBase, doesn't make a difference -- no one else can connect, get the RBase message about "cannot connect to database, might be open with multi off". But no one is connected. That person is able to get back in, and open multiple copies of the database at the same time. When we tried to copy in a good backup copy, only that person is able to erase the database. So we had that person erase the database, brought in the backup, had a different person connect to the database, and same thing -- now that person is the only one who can get into the database. Even if they exit, no one else can get in. To me, this points to a network issue beyond RBase's control, but I'm getting pushback from their IT. On Monday I'm going to ask them to replace the 6.5++ software directory with a backup from before we had these problems in case the software network control itself is messed up. This was so long ago I forget -- is there a particular program that controlled network access (I remember the old server.sy5 but I think that was earlier versions). If that doesn't work, I might try connecting to the database with the upgraded version and see if that works and allows anyone else to connect. Is there anything in the database itself that could cause this "lock" to never be released or for the database to behave as single-user even though it was opened with multi on and that user can open multiple copies? Do I keep pushing their IT that this is their issue? Boy, I hate stuff like this.... Karen
