I have this designed in Access 97 now but as we add more users we are having problems...
Question...How will SQL Server specifically solve the double records problem??
Main Problem: I need to serve out continous records to each workstation every 30 secs or so without two workstations getting the same record...will SQL Server help solve this problem??
Right now a workstation gets the next record (when the user clicks next) where called = False but if two workstations request a record at the same time...they both get the same record.
Overview
Two tables (connected by callerID)
1) tblClients (callerID, name, address, phone numbers etc)
2) tblRecords (response, Date of Call, Time of Call, comments)
Backend to be on Server....frontend of 10 workstations (to be more soon)
tblClient needs to serve out one record after another 1..2..3..4 to whatever workstation requests a new record.
Two workstations can't get the same record.
10 workstations will be running at the same time and each workstation will probably request a new record every 30 secs - 1 minute.
Other points...
Right now we have 4 client tables with approx 50 000 records each. (could increase)
Right now I am getting workstations receiving the same record from the server about 2-5% of the time. (depending on the number of users 5-10)
How will SQL Server specifically solve the double records problem?? If so how??
Thanks in advance![[wiggle]](/data/assets/smilies/wiggle.gif "[wiggle] [wiggle]")
eclipse33
Question...How will SQL Server specifically solve the double records problem??
Main Problem: I need to serve out continous records to each workstation every 30 secs or so without two workstations getting the same record...will SQL Server help solve this problem??
Right now a workstation gets the next record (when the user clicks next) where called = False but if two workstations request a record at the same time...they both get the same record.
Overview
Two tables (connected by callerID)
1) tblClients (callerID, name, address, phone numbers etc)
2) tblRecords (response, Date of Call, Time of Call, comments)
Backend to be on Server....frontend of 10 workstations (to be more soon)
tblClient needs to serve out one record after another 1..2..3..4 to whatever workstation requests a new record.
Two workstations can't get the same record.
10 workstations will be running at the same time and each workstation will probably request a new record every 30 secs - 1 minute.
Other points...
Right now we have 4 client tables with approx 50 000 records each. (could increase)
Right now I am getting workstations receiving the same record from the server about 2-5% of the time. (depending on the number of users 5-10)
How will SQL Server specifically solve the double records problem?? If so how??
Thanks in advance
eclipse33
