Saving a standalone

[Richard Gaskin]

Shari wrote:

>> Recently, Simon Lord wrote:
>> 
>>> Is it possible to have a standalone make changes to itself and
>>> actually save those changes?
>> 
>> Nope.  You can only edit/save (non-standalone) stacks.  You can get close to
>> what you ask by keeping the bulk of your scripts in a stack and using a
>> small standalone engine to run the stack -- changes are save by the engine
>> to the stack.
>> 
>
> Doesn't that defeat the purpose of using a standalone?  Anything in
> the stack, can't it be opened etc. by anyone with Metacard?  The
> purpose of using a standalone besides convenience, is to protect the
> data, scripts, imports, etc. from anyone with prying eyes.  Yes you
> can script some protective things into a stack, but the whole purpose
> of having a standalone is for the extra protection it offers.

Such protections are afforded all password-protected stacks, standalone or
not.

Standalones not password protected can, with some work, still be edited with
MetaCard.

-- 
 Richard Gaskin 
 Fourth World Media Corporation
 Custom Software and Web Development for All Major Platforms
 Developer of WebMerge 2.0: Publish any Database on Any Site
 ___________________________________________________________
 Ambassador at FourthWorld.com       http://www.FourthWorld.com
 Tel: 323-225-3717                       AIM: FourthWorldInc