Visual Basic&database, Jet Engine Multi-User features

Jet Engine Multi-User features

Author	Message
Scott Schlesi #1 / 5	Jet Engine Multi-User features I am currently in the process of converting a stand alone VB application using Access 2.0 tables to a multi-user application. I would like to use optimistic locking for all of the data access in this application, however; I have been running into some problems. Immediately after opening any recordset I set it's LockEdits property to false ot allow for optimistic locking. Unfourtunately this does not seem to be working. As soon as I place a record into edit mode on one machine I am unable to place the same record into edit mode on any other machine. I receive Error 3260 Couldn't update locked by ... Are there any other properties besides LockEdits which need to be set to enable optimistic locking? Can anyone point me to a good reference on multiuser issues in VB4? Scott.
Mon, 19 Jul 1999 03:00:00 GMT

S.Sund #2 / 5	Jet Engine Multi-User features Quote: >I am currently in the process of converting a stand alone VB >application using Access 2.0 tables to a multi-user application. I >would like to use optimistic locking for all of the data access in >this application, however; I have been running into some problems. >Immediately after opening any recordset I set it's LockEdits property >to false ot allow for optimistic locking. Unfourtunately this does >not seem to be working. >As soon as I place a record into edit mode on one machine I am unable >to place the same record into edit mode on any other machine. I >receive Error 3260 Couldn't update locked by ... >Are there any other properties besides LockEdits which need to be set >to enable optimistic locking? Can anyone point me to a good reference >on multiuser issues in VB4? >Scott. As far as know from my collegues - they did a project with VB and Access 2.0, , Access 2.0 Jet Engine Multi-user features are screwed-up; esp. if you need referential integrity. Secondly it will be slowdown in multi-user environment. If you have referential integrity set, remove and try. If you need ref. integriy and password protection then go far paradox table. It would be safer and reliable. - Enjoy. :-) S.Sundar
Mon, 19 Jul 1999 03:00:00 GMT

Phil Tra #3 / 5	Jet Engine Multi-User features Scott: Because you are converting from a stand-alone mdb, I'm tempted to think your MDB is in exclusive mode. Go to Tools>Options and set your MDB to shared. Also if you're running Win3.1 check your config.sys for FCBS=16,8 and Files=50. Your Autoexec.bat should have "Share.exe /l:500 /f:5100" loaded.
Tue, 20 Jul 1999 03:00:00 GMT

Derek Mort #4 / 5	Jet Engine Multi-User features :> :>I am currently in the process of converting a stand alone VB :>application using Access 2.0 tables to a multi-user application. I :>would like to use optimistic locking for all of the data access in :>this application, however; I have been running into some problems. :>Immediately after opening any recordset I set it's LockEdits property :>to false ot allow for optimistic locking. Unfourtunately this does :>not seem to be working. :> :>As soon as I place a record into edit mode on one machine I am unable :>to place the same record into edit mode on any other machine. I two people cannot edit the same record at the same time, the second save will overwrite the first resulting in lost data... Derek :>receive Error 3260 Couldn't update locked by ... :> :>Are there any other properties besides LockEdits which need to be set :>to enable optimistic locking? Can anyone point me to a good reference :>on multiuser issues in VB4? :> :>Scott. :> // Derek Morton and Lenise Whyte in Eltham, Australia //
Tue, 20 Jul 1999 03:00:00 GMT

Hong YA #5 / 5	Jet Engine Multi-User features Quote: > I am currently in the process of converting a stand alone VB > application using Access 2.0 tables to a multi-user application. I > would like to use optimistic locking for all of the data access in > this application, however; I have been running into some problems. > Immediately after opening any recordset I set it's LockEdits property > to false ot allow for optimistic locking. Unfourtunately this does > not seem to be working. > As soon as I place a record into edit mode on one machine I am unable > to place the same record into edit mode on any other machine. I > receive Error 3260 Couldn't update locked by ... > Are there any other properties besides LockEdits which need to be set > to enable optimistic locking? Can anyone point me to a good reference > on multiuser issues in VB4? > Scott. Scott: I would suggest that you do this: In your error handle lines, check if the error code is 3260. If it is, display a msgbox and ask the user if he wants to try again. If he does, save it again.
Wed, 21 Jul 1999 03:00:00 GMT

Page 1 of 1

[ 5 post ]