DB Access in standalones

Tuviah Snyder tuviah at runrev.com
Wed Aug 20 05:54:00 EDT 2003


> Message: 8
> Date: Tue, 19 Aug 2003 23:09:10 -0500
> From: "J. Landman Gay" <jacque at hyperactivesw.com>
> Organization: HyperActive Software
> To: use-revolution at lists.runrev.com
> Subject: Re: DB Access in standalones
> Reply-To: use-revolution at lists.runrev.com
>
> On 8/19/03 6:06 PM, Trevor DeVore wrote:
>
> > I had problems with database access in standalones at one point but was
able to get everything working.  Here is how my project is set up-
> >
> > 1) I have one splash stack whic his used to create the executable
(splash.rev)
> > 2) The main program (program.rev) and two additional pop-up windows are
.rev files stored external to the executable.
> > 3) The main program has a sub stack which has all of the database calls
(database.rev).
> > 4) When the executable launches it opens program.rev and hides itself.
> >
> > At first, program.rev would simply start using database.rev and that
worked fine in the Rev development environment.  When I built the
Well one thing that you can try is to insert the script of the stack that
has the externals property into front, or back. Currently what's happening
is that Rev sets the externals in the dev environment in such a way that it
is available to all stacks...so it works in dev but may not work in
standalones. The team is working to resolve these issues..but if you have a
recipe and can send sample stacks please send to bugzilla and mark them
something of high priority if they interfare with you using RevDB.

Tuviah Snyder <tuviah at runrev.com> <http://www.runrev.com/>
Runtime Revolution Limited - Software at the Speed of Thought




More information about the use-livecode mailing list