Record Locking - Against SQL Server

I'm using VB6 against an SQL Server 7 database.
I'm having trouble coding for a case where more than one user is accessing the same record.
If a user makes changes to the record and saves the record, the record should be saved and refreshed on the server.
The application consists of a datagrid in which the user can double-click on a record in the grid to make changes.
Then, a form is brought up to allow the user to make changes.
The way the code is written now is this:
After the user exits the form after having made changes, I run the same sql statement again to refresh and populate the grid.
But, this isn't working.
The update is only working on the machine where the user made the changes.
On other client computers accessing the grid at the same time, the changes aren't updated.

Is there some sort of commit I need to make to save all of the changes up-to-the-minute?

Thanks in Advance
John
jtrapat1Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Anthony PerkinsCommented:
Are you using the ADO Data Control?  If so, this might explain the problem.

Anthony
0
inthedarkCommented:
There is an issue here with the way that multiple users are responsible for the same data.  What type of application is it? Could the user's responsibilities be divided?
0
dgorinCommented:
You could try a CursorType property of 2 in your ADODC or the code that opens your recordset.  If you're using ADO, anyway.
0
The Ultimate Tool Kit for Technolgy Solution Provi

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy for valuable how-to assets including sample agreements, checklists, flowcharts, and more!

jtrapat1Author Commented:
I'm not using the ADO data control.
I'm using a recordset as a data source for the datagrid and it's still not updating for each concurrent user.

This is a client-server application.


0
jtrapat1Author Commented:
I'm not using the ADO data control.
I'm using a recordset as a data source for the datagrid and it's still not updating for each concurrent user.

This is a client-server application.


0
barendbCommented:
You need to requery all users' recordsets periodically, because they will only see data up to the last change that they have made.  Try the following, update a record on one user's machine, save changes.  Now update another record on another user's machine and save the changes, you should be getting botth changes back on the second machine, because you requery after the update.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Visual Basic Classic

From novice to tech pro — start learning today.