Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
chilluk
Starting Member
24 Posts |
 Posted - 2004-12-06 : 09:24:01
|
| I've got a SQL Server 2000 back end, with Access 97 (the client doesn't want to spend the money on Office upgrades) linked by ODBC using a System DSN. There are around 40 users with a mixture of NT Workstation and Win 98. The back end db consists of 2 main tables, and about 20/30 reference and system tables. The forms are all bound to the linked tables.Occasionally we have the scenario where the users are merrily updating the system, and for one reason or another (most recent was the network admin clogged up the server disk space by dumping 40Gb of data on it, so the db could not grow any more!!) the updates do not "take". However they do not get an error message at the client end indicating this so between the 40 users they can lose several hundred small updates before anyone notices.Access allows them to close the form and go onto the next record so I assume all events are firing etc - maybe the updates are just getting queued up on the server which is then struggling to apply them to the db?Are there any settings that can be tweaked to ensure problems come to light more quickly? Or any other ideas to ensure that the changes have taken. To get over the issue of them using up "my" disk space I increased the db size to well in excess of what I need to "reserve" my capacity - however I have seen similar behaviour just before the server falls over etc - there seems to be a lag between the problem starting and any kind of notification.The main tables have timestamp columns - I was thinking of reading this in when the record is loaded, and then checking it again in the after_update event on the forms - if it has changed I am assuming I can safely be sure that the record has been changed???EDIT : Apologies for that - the script was timing out - can the Mods please delete the dupe posts thanks |
|
|
|
|
|
Updates Fail with no error message