D
Dominic Belley
Hi,
In my VB.NET app, I initialize a connection when the application is loading.
Case scenario here:
Operation 1- I go into my "Member Management" winform and search for the
Membre #2.
That creates a BEGIN transaction ...calls a stored proc with (UPDLOCK) to
have the record locked to others and fill a dataset.
With that dataset I fill the winform input fields ... Then the user then
takes the time to make changes to the membre #2 file ...
Operation 2- The user then go into my "Tables Management" winform .... still
having the transaction in operation 1 not being committed or rollbacked yet
... he just want to see other info in another screen while he's doing
operation 1.
In that 2nd screen, when I populate a dataset, I always get the error
mentionned in the subjet.
---
The only way for me to avoid that is to commit or rollback the transaction
of operation 1 before doing another select from a database table.
But this is bad .. I absolutely need to be able to open many winforms at the
same time.
How can I avoid this problem?
Using many connection to my database? So I could have 1 dedicated for each
winform I need to do a BEGIN TRANSACTION that remains open for a long while
? (as long as the user makes is changes and saves(commit) or
cancel(rollback) his transaction ?
Sometimes he can open the Operation 1 screen and only commit at the end of
the day ..
---
The real question is .. with only one SQLConnection .. is it possible to
have it used in a winform that performed a BEGIN TRANSACTION which remains
active (uncommitted or rollbacked ) for a long period ... and during that
period, open another winform .. and use the same SQLConnection to perform
another query to my database?...
Thanks for helping me on this ...
In my VB.NET app, I initialize a connection when the application is loading.
Case scenario here:
Operation 1- I go into my "Member Management" winform and search for the
Membre #2.
That creates a BEGIN transaction ...calls a stored proc with (UPDLOCK) to
have the record locked to others and fill a dataset.
With that dataset I fill the winform input fields ... Then the user then
takes the time to make changes to the membre #2 file ...
Operation 2- The user then go into my "Tables Management" winform .... still
having the transaction in operation 1 not being committed or rollbacked yet
... he just want to see other info in another screen while he's doing
operation 1.
In that 2nd screen, when I populate a dataset, I always get the error
mentionned in the subjet.
---
The only way for me to avoid that is to commit or rollback the transaction
of operation 1 before doing another select from a database table.
But this is bad .. I absolutely need to be able to open many winforms at the
same time.
How can I avoid this problem?
Using many connection to my database? So I could have 1 dedicated for each
winform I need to do a BEGIN TRANSACTION that remains open for a long while
? (as long as the user makes is changes and saves(commit) or
cancel(rollback) his transaction ?
Sometimes he can open the Operation 1 screen and only commit at the end of
the day ..
---
The real question is .. with only one SQLConnection .. is it possible to
have it used in a winform that performed a BEGIN TRANSACTION which remains
active (uncommitted or rollbacked ) for a long period ... and during that
period, open another winform .. and use the same SQLConnection to perform
another query to my database?...
Thanks for helping me on this ...