![]() ![]() In the console tree, click Connections.To open the Terminal Services Configuration Tool, click Start, point to Administrative Tools, and then click Terminal Services Configuration. ![]() How to limit the number of remote sessions on a terminal server By default, with a Windows Server 2003 terminal server in Remote Administration mode, you can have two remote sessions and one console session, for a total of three active sessions. This article describes how to make sure that only one user at a time can connect to a Windows Server 2003 terminal server in Remote Administration Mode remotely or at the console. Expect lots of support calls with this scheme.This article describes how to make sure that only one user at a time can connect to a Windows Server 2003 terminal server in Remote Administration Mode remotely or at the console.Īpplies to: Windows Server 2003 Original KB number: 830581 Summary if someone logs into the database and then rips the power cord out of the wall, the database will be 'locked' permanently until you fix it. * The 'lock the file in a table row "semaphore"' is a bad idea because the semaphore never unsets-i.e. If your users are abusing this feature, then you need to get their manager to explain to them that this is not ok.I just don't see the problem. One of the awesome features about Access is that it warns the user when they're about to 'overwrite' someone else's changes. * Why is this a problem in the first place? This shouldn't be a problem. Set everyone's machine/profile to try to open the db in Exclusive Mode, and you're done. You can set this in Access (File->Open) and (my guess is) this is probably stored in the registry, so you can set it from there as well. All other users will be prompted, noting that the database is locked and that they will not be able to edit records. * Access allows you to open the file in "Exclusive Mode" - this is an option that allows one person to lock the database for their use only. Read up on optimistic and pessimistic record locking (help files). * Access has record-locking, so this isn't necessary. So here are some things I want to explain: This is probably a flawed question - they shouldn't be asking you to do this. RE: Allow only one person to modify database at a time Keetso (TechnicalUser) Please let me know if you need any add'l info. I made sure that the "Default Open Mode" on the database is set to "Exclusive" but they are all still able to open the database and add/modify/delete data at the same time. If either of the other two (or both of them) opens the database while one is already in, they will only have read-only rights at that time.Įmployee "A" - Opens DB first and is entering dataĮmployee "B" or "C" - Opens DB during this time but onlyĮmployee "A" - Finishes, closes DB and informs Employee "B"Įmployee "B" or "C" - Can then re-open the database and ![]() What they want to do is to allow only one of the three employees at a time to be able to add/modify/delete data. "B" and "C" has created shortcuts on their own desktops to this folder. A single, stand alone database is located in a folder on Employee "A"s network share called, for lack of better words, "AccessDB".Įmployee "A" has given full rights to the "AccessDB" folder to Employee "B" and "C". ![]()
0 Comments
Leave a Reply. |