I am planning to create a collaborative work group situation and before starting want to know something I could try by testing, but would rather know even before planning out the stack architecture. It is simply this: 1) Can you assign a stack to be a stack file of multiple main stacks? i.e. Can stack Z be a stack file for main stacks 1 2 3 and 4? 2) Are stack files that are assigned to a mainstack in an "open file" state when the mainStack is open? I would assume not. and that if 1) above is true, that if the stack file is closed, the read/write privileges would be available to the next user whose mainstack was to access the stack file. The idea is to simulate a multi-user situation where a stack file would appear like "This record is in use" in a multi-user dbase situation if it were open. We would test for it not being available in and inform the user, if the stack closes it broadcasts itself as being closed and now available Right now I have a single Supercard web page engine that has to be closed out/quit out by one person before another person can use it, but now there are about six staff members involved in the html generation and when I convert this SC engine over to MC I want to break out the tasks in a way that each department can work on it separately. The final builds of the pages will then access the stack files, but with very with quick I/0's just to access finished code chunks. If anyone else is doing this kind of thing, any advance insights on the overall stack architecture will be appreciated. Hinduism Today Sivakatirswami Editor's Assistant/Production Manager [EMAIL PROTECTED] www.HinduismToday.com, www.HimalayanAcademy.com, www.Gurudeva.org, www.hindu.org Archives: http://www.mail-archive.com/[email protected]/ Info: http://www.xworlds.com/metacard/mailinglist.htm Please send bug reports to <[EMAIL PROTECTED]>, not this list.
