On Aug 2, 2004, at 12:11 PM, [EMAIL PROTECTED] wrote:
PLATFORM: MacOSX (10.3.4)
ISSUE: MySQL commands not working
DESCRIPTION: We have a small, standalone "client" Rev app (MacOSX
10.3.4) that shows a splash screen and calls a separate .rev main stack,
which is the main guts of the application. The client app is on the
user's Mac (>40 users), and the .rev main stack is on the server. This
way, when we make changes/updates to the application, everyone is running
the latest version. The main application uses MySQL commands. The MySQL
commands work fine in development mode, and if I build it as a standalone
app. However, the MySQL commands do not work when the .rev main stack
(not a standalone) is called by the client app. I have set my standalone
settings for the client app to include the MySQL Database Support.
I imagine that the revdb external is being applied to to the stack (splash) that is being used to create the executable. In your client stack start using the stack that was used to create the exe. So if your splash stack was named "mySplash" then in your client stack do something like this:
start using stack "mySplash"
This will make the revdb calls available in the message path.
-- Trevor DeVore Blue Mango Multimedia [EMAIL PROTECTED]
_______________________________________________ use-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/use-revolution
