To view the terms under which this email is distributed, please go to
http://disclaimer.leedsmet.ac.uk/email.htm
On 30 November 2004 14:45, SCALES, Andrew wrote:
> Thanks very much for your help. The main difficulty I was
> having really was
> unlocking the record again if the user crashed out
uot; repeatedly that you have issues. :)
Good luck!
-TG
> -Original Message-
> From: SCALES, Andrew [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, November 30, 2004 9:45 AM
> To: [EMAIL PROTECTED]
> Subject: RE: [PHP-DB] Multi-User Update Problem
>
>
> Thanks very m
just try that.
Thank you both for the advice,
Andy
-Original Message-
From: Gryffyn, Trevor [mailto:[EMAIL PROTECTED]
Sent: Monday, 29 November 2004 15:44
To: [EMAIL PROTECTED]
Cc: Bastien Koert; [EMAIL PROTECTED]
Subject: RE: [PHP-DB] Multi-User Update Problem
Yeah, all good tho
our suggestions though.
Andy
-Original Message-
From: Norland, Martin [mailto:[EMAIL PROTECTED]
Sent: Monday, 29 November 2004 15:36
To: [EMAIL PROTECTED]
Subject: RE: [PHP-DB] Multi-User Update Problem
-Original Message-
>Does anyone know a good way of locking out access to a r
to get into
them again if they "time out".
-TG
> -Original Message-
> From: Bastien Koert [mailto:[EMAIL PROTECTED]
> Sent: Monday, November 29, 2004 10:22 AM
> To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
> Subject: RE: [PHP-DB] Multi-User Update Problem
>
>
&
-Original Message-
>Does anyone know a good way of locking out access to a record on a
>MySQL database when someone has the update page open? The problem is
>that we have a local intranet site which is accessed by members of
>different departments. Now at the moment when someone loads t
Its a tough one. My personal fav is to mark the record as locked by changing
a field called 'locked' from 0 to 1. Check for this when extracting the
record and if is present, alert the user this record is locked (if you want
to get fancy you could even track who locked it and the tell the user t
