Using stacks as a database for very large data sets

[Lynch, Jonathan]

For me it would work, because, although the stack may be used by
different people on different computers - it would never be used by
different people at the same time.

Only one of us would compose the Media Tracking Report on any given day.


-----Original Message-----
From: use-revolution-bounces at lists.runrev.com
[mailto:use-revolution-bounces at lists.runrev.com] On Behalf Of Kurt
Kaufman
Sent: Wednesday, January 26, 2005 6:24 PM
To: use-revolution at lists.runrev.com
Subject: Using stacks as a database for very large data sets


"...In that case you could copy the file onto your HD temporarily, edit
and then copy it back to the server..."

Would something like this work? There would be two versions of the 
splash-stack, one for User-A, and another for User-B, C, etc.

User-A  opens splash-stack and data-stack.
               -dataStackInUse is set to true --flag
(User-B cannot open stacks)

User-A is finished with stacks.  Closes.
               -dataStackInUse is set to false

User-B may now open splash-stack and data-stack.
              -splash-stack and data-stack are automatically copied to 
computer B.
              -dataStackInUse is set to true
(User-A cannot open stacks)

User-B is finished with stacks.  Closes. --but before closeStack, the 
following:
              -splash-stack and data-stack are automatically copied back

to computer A.
               -dataStackInUse is set to false

_______________________________________________
use-revolution mailing list
use-revolution at lists.runrev.com
http://lists.runrev.com/mailman/listinfo/use-revolution