On 19/9/01 4:21 pm, Devin Asay <[EMAIL PROTECTED]> wrote:
> What I found in essence was that if more than one person has opened
> the same stack for editing, the only changes that ultimately get
> saved are those of the *last* person to save. For example, user 1
> opens the stack from the file server and begins editing, then user 2
> opens the same stack and begins editing. Let's say user 1 adds a
> card and enters data into that card's fields, then saves and closes
> the stack and purges it from memory. User 2 also creates a new card
> and enters data into its fields, then saves and closes and purges it
> from memory. The next person to open that stack will only see the
> changes made by user 2; no trace of user 1's work remains.
>
> Is that expected behavior, or have the developers even looked at this issue?
This is the expected behaviour, because a stack is loaded into memory when
it is opened and then written back to the disk.
You can write a lock file (just a text file) to the directory the stack is
in on opening, then delete it on closing. When opening check for this file,
if present the stack is open on another machine so bring up a warning dialog
and exit. If you want multiple users to be able to work on a stack at once,
you need to run the stack as a server and write clients to it which send
information via sockets, so that just that one stack receives and saves the
data into itself. We are aware that it would be desirable to improve this
at the Revolution level, but such a change is complex and is therefore not
planned in the immediate term.
Regards,
Kevin
Kevin Miller <[EMAIL PROTECTED]> <http://www.runrev.com/>
Runtime Revolution Limited - Power to the Developer!
Tel: +44 (0)131 718 4333. Fax: +44 (0)1639 830 707.
