Multiuser or not multiuser
William de Smet
williamdesmet at gmail.com
Fri Nov 16 03:56:41 CST 2007
Thanks for your replies,
A database engine is not what I need because I don't know how to do it. I
will stick with TXT files.
If I follow Henks suggestion I will export every users choice as a seperate
But how do I collect these?
I know how to import just one textfile but how do I import more than one
They will look like this: date_name.TXT
William de Smet
2007/11/15, Henk van der Velden <henk at iglow-media.nl>:
> Hi William,
> 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,
> 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.
> use-revolution mailing list
> use-revolution at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
More information about the use-livecode