On Jan 3, 2004, at 8:44 PM, J. Landman Gay wrote:
This sounds like the common problem where the database external is not loading at all in the substack. When the splash opens (the mainstack) it loads the external, but when you close the splash, the external gets unloaded. Then when the substack opens, there is no external available for the substack.
You can try adding the database to the externals property of the substack and sometimes that will work. Sometimes it doesn't. You can also try hiding the splash instead of closing it; maybe that will force the external to stay resident in memory. Or you can try moving all your database handlers into the splash stack script, where they will be available everywhere.
I have entered a Bugzilla enhancement request that asks that we be able to load externals on demand. That would solve this problem, which seems to affect just about everybody who tries to use a splash for the application mainstack with a substack that uses an external. It isn't just databases either, it happens with any external.
Jacqueline,
This is a most usefull reply! Thanks all try the options and post here the updates so others might see how to proceed in cases like this.
Cheers
Andre Alves Garzia 2003 BRAZIL http://www.soapdog.org
_______________________________________________ use-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/use-revolution
