Multiuser or not multiuser

[Henk van der Velden]

Hi William,

goeiemiddag..

Indeed, the other question is how to approach the multi-user issue in  
this case.
Blocking clients like this can be a bit unfriendly, and it also poses  
issues when the 'inuse' variable isn't saved properly. You could end  
up with a completely blocked application.

One approach could be to use a database. Database engines have their  
own record blocking mechanisms, so one user can't overwrite the  
record of another user.

Or, if you don't want to setup a database, you could probably create  
a folder on every day, and have each user add his / her own textfile  
to that folder. If you put both the username and the chosen lunch  
into the file, a user could eventually turn back and change his choice.
You could create another app that collects all the text files and  
creates a list out of it.

Kind regards,
Henk


On 15-nov-2007, at 15:56, use-revolution-request at lists.runrev.com wrote:

> Because the app is put on a Server 2003 with XP clients it needs to be
> multiuser or not.