Some little questions about Data Stacks

[Rob Cozens]

Bonjour, François

>So, all my data are in a stack that is not include in the builder. It's
>correct? Yes? OK, it works by me... I'm able to open the stack and to save
>the modifications, in Windows too.

Yes, just have the distribution builder maintain the stack as a 
separate file from the standalone.

>
>I have read the Tutorial Independent Study. If I have well understood, the
>external stack (with data) must have the".edb" extension?

To the best of my knowledge, an external stack can have whatever 
extension you script support for.  SDB databases, for example, use 
the extension, ".sdb".

>
>And please, how to protect the stack with data, in order to prevent any user
>to open the stack without to pass by my application. But I want to be able
>to open the stack from the app, of course!

Possibly you could check for the name of the app opening the stack in 
its preOpenStack logic.  Of course, any stack that includes a general 
"open stack" menuItem will be filtering for ".rev" (& file 
type/creator "RSTKRevo" on Mac OS); so if you assign you own 
extension & file type to the data stack, it won't be seen on a 
general RunRev answer file dialog.  You can also add password 
protection to your data stack so if someone opens it accidentally 
they wont be able to view or modify it unless they already know the 
stack & its password.

>
>Finally, is it possible to open the stack in background to prevent the user
>to see it?

'go invisible to stack "MyHiddenStack"'...

or simply get data from the stack without going to it (al la SDB -- 
most handlers);

'get field "Some Needed Info" of card currentCardNumber of stack "My 
Hidden Database"'

Hope this helps.

-- 

Rob Cozens
CCW, Serendipity Software Company
http://www.oenolog.com/who.htm

"And I, which was two fooles, do so grow three;
Who are a little wise, the best fooles bee."

from "The Triple Foole" by John Donne (1572-1631)