Hi,
I'm just after some general comments & opinions to see if I'm heading down the right track. I have a database application for about six users, but it runs on Terminal Server. The record locking doesn't work. Access seems to use the machine name to distinguish users, but these users all have the same one!
On two or three occasions, I've had a corrupted table from a record conflict. One way round it that seemed to work was adding a save record command after most of the fields on the form, but that's rather ugly.
I've now developed a user table with fixed records that get updated by the main form. Essentially, open the form, use a recordset to find the currentuser in the user table & enter the record number in an appropriate field.
I now get it to check the other records first & if it finds the current record number, lock the form. Works well. If someone tries to open a record already in use, they get a polite sod off message!
It's far from perfect, but has worked so far. Can anyone offer anything better for a Terminal Server environment? Or record locking in general. I've assumed a lot about this & may have misunderstood. Plus, I use a lot of recordsets; as the standard record locking is being ignored, is this still a weak spot?
Cheers!
Jon
I'm just after some general comments & opinions to see if I'm heading down the right track. I have a database application for about six users, but it runs on Terminal Server. The record locking doesn't work. Access seems to use the machine name to distinguish users, but these users all have the same one!
On two or three occasions, I've had a corrupted table from a record conflict. One way round it that seemed to work was adding a save record command after most of the fields on the form, but that's rather ugly.
I've now developed a user table with fixed records that get updated by the main form. Essentially, open the form, use a recordset to find the currentuser in the user table & enter the record number in an appropriate field.
I now get it to check the other records first & if it finds the current record number, lock the form. Works well. If someone tries to open a record already in use, they get a polite sod off message!
It's far from perfect, but has worked so far. Can anyone offer anything better for a Terminal Server environment? Or record locking in general. I've assumed a lot about this & may have misunderstood. Plus, I use a lot of recordsets; as the standard record locking is being ignored, is this still a weak spot?
Cheers!
Jon
