Updating Data Substacks

[Dan Shafer]

It just occurred to me that the RR model which requires me to create 
a separate stack to hold the data for my app might be an obstacle to 
product upgrades.

My mainstack is a splasher. My substacks are a palette (which can 
change) and the primary data stack (which will change). If in my next 
rev of the product, I wish to add features (e.g., a menu or even a 
button on that stack with some new functions), I would expect to ask 
my users to replace their current stack with the new one. But that 
will, obviously, result in the loss of all their data.

How should this work? What am I missing?
-- 
-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-
Dan Shafer
Technology Visionary - Technology Assessment - Documentation
"Looking at technology from every angle"
http://www.danshafer.com
831-392-1127 Voice - 831-401-2531 Fax