David Bovill wrote:
>
> How can you tell when you have made changes to the stack in memory and therefore
>need to save it when it is closed. Do you have to tracke every change? The save
>command seems to save even when you have done nothing - right.
>
> Can you do something fancy like an MD5digest of the stack in memory??? The issue is
>that it takes a long time to save a database stack as it gets large, and I don't want
>to loose data. What's the best strategy?
>
David,
Try :
on openstack
global OState
put "0" into OState
add length(firstcontainertocheck) to OState
add length(secondcontainertocheck) to OState
...
end openstack
on closestack
global OState
put "0" into eState
add length(firstcontainertocheck) to eState
add length(secondcontainertocheck) to eState
...
if length(OState) is not length(eState)
then save this stack as thepathtostack
end closestack
Best Regards, Pierre Sahores
WEB, DB, B2B & ASP design.
There are countries where people
have six fingers because they
don't know the metric system.
Sir Jean Yanne
Archives: http://www.mail-archive.com/metacard%40lists.best.com/
Info: http://www.xworlds.com/metacard/mailinglist.htm
Please send bug reports to <[EMAIL PROTECTED]>, not this list.
