-----Original Message-----

From: Rudy Steyaert [mailto:Rudy.Steyaert@c...]

Sent: 26 June 2000 17:00

To: Feedback

Subject: Beginning ASP Databases 2726





Hello,

 

Similar to the example described starting on page 314 I am building a few 

pages to update a record.

 

The problem I have now is, how can I be sure that nobody changes the 

information in the record between the time I present the current data to 

the user and the moment the user submits his changes ?  So, to be clear, 

the record is read, and presented to the user in a form.  Then, the user 

takes the time he needs to check and eventually change the data.  Of 

course, in the meantime, another user could have the same idea and start 

the same process.

 

In a regular C++ application we would lock the record as soon as it is read 

and for the time it is beiing edited - until the user cancels or confirms 

his changes.

 

Within the same ASP-application I could create some application-semaphore 

alike thing, but when it comes to several different applications (not 

necessarily ASP-applications) I can't think of a way to lock a record let's 

say in a classic way ?



Perhaps you can ?

 

Thanks in advance and regards

Rudy Steyaert

Phil,



If you use SQL Server 6 or 7, you can give a "lock hint" to the 

database.



Charles





-----Original Message-----

From: Phil Perks [mailto:philp@w...]

Sent: 26 juin, 2000 08:00

To: ASP Databases

Subject: [asp_databases] ASP Databases





-----Original Message-----

From: Rudy Steyaert [mailto:Rudy.Steyaert@c...]

Sent: 26 June 2000 17:00

To: Feedback

Subject: Beginning ASP Databases 2726





Hello,



Similar to the example described starting on page 314 I am building a 

few

pages to update a record.



The problem I have now is, how can I be sure that nobody changes the

information in the record between the time I present the current data 

to

the user and the moment the user submits his changes ?  So, to be 

clear,

the record is read, and presented to the user in a form.  Then, the 

user

takes the time he needs to check and eventually change the data.  Of

course, in the meantime, another user could have the same idea and 

start

the same process.



In a regular C++ application we would lock the record as soon as it is 

read

and for the time it is beiing edited - until the user cancels or 

confirms

his changes.



Within the same ASP-application I could create some 

application-semaphore

alike thing, but when it comes to several different applications (not

necessarily ASP-applications) I can't think of a way to lock a record 

let's

say in a classic way ?



Perhaps you can ?



Thanks in advance and regards

Rudy Steyaert