Have anyone here used this? I was hoping to find someone here who has actually used this sort of table locking and unlocking. Thanks.
On Nov 7, 10:33 pm, Benj Nunez <[email protected]> wrote: > You can use transaction as demonstrated > here:http://www.dotnetspider.com/resources/18138-Locking-Table-SQL-SERVER-... > > Regards, > > Benj > > On Nov 4, 10:49 pm, Davej <[email protected]> wrote: > > > I'm looking for a basic outline of the steps that are usually used in > > a multi-user database app. So far I've only played with the single- > > user situation, so when I load the form I load the form's datagrid... > > > Try > > Me.TblMy_TableTableAdapter.Fill(Me.My_DBDataSet.tblMy_Table) > > Catch ex As Exception > > MsgBox("Database Error: " & ex.Message) > > End Try > > > And then when the user exits the form I simply save... > > > Try > > Me.Validate() > > Me.TblMy_TableBindingSource.EndEdit() > > If Me.My_DBDataSet.HasChanges = True Then > > If MsgBox("Post Edits to Remote Database?", MsgBoxStyle.YesNo, > > _ > > "UPDATES PENDING") = MsgBoxResult.Yes Then > > Me.TableAdapterManager.UpdateAll(Me.My_DBDataSet) ' update > > remote database > > End If > > End If > > Catch ex As Exception > > MsgBox("Database Error: " & ex.Message) > > End Try > > Me.Close() > > > Now what is the outline of the save operation for a simple non- > > cascading multi-user situation? I'm thinking you probably want/need to > > identify your updates, inserts and deletes and then go through some > > sort of read-lock-write-unlock loops? I have no idea. I have no > > exposure to this more complex stuff at all. > > > Thanks, > > > Dave
