revOpenDatabase acting differently in IDE and standalone

Mike Bonner bonnmike at gmail.com
Wed May 1 17:11:43 EDT 2013


Another thought, (again 98% sure this isn't the issue but..)  If the
standalone builder picks and chooses db support based on code it sees in
the stack, and if you are using a splash stack, or your db code is in a
substack/external stack, is it possible that the standalone builder is just
not including the postgres dll?   To test this theory you might go into the
standalone settings and manually pick your inclusions, checking database
support and selecting postgresql. Even if everything is in the main stack
it wouldn't hurt to test it this way as an elimination step.


On Wed, May 1, 2013 at 3:07 PM, Mike Bonner <bonnmike at gmail.com> wrote:

> Hmm, based on the error you posted i'm sure this isn't the issue, but..
> you aren't trying to open the postgres database in preopenstack are you?
>  If so, externals loading may not yet be complete.
>
>
> On Wed, May 1, 2013 at 3:02 PM, Dr. Hawkins <dochawk at gmail.com> wrote:
>
>> On Wed, May 1, 2013 at 1:55 PM, Peter Haworth <pete at lcsql.com> wrote:
>>
>> > Maybe I'm misunderstanding the requirement here, but aren't you sending
>> > this application out as a standalone?  If so the issue of password
>> > protecting the scripts is moot since it only applies to running stacks
>> in
>> > the IDE.
>> >
>>
>> Yes, but if I send it out without the password protection, anyone could
>> open it with the IDE, couldn't they?
>>
>>
>> > Doesn't help with your revdatabaseopen problem though.
>> >
>>
>> which is the one killing me right now :)  I can't even put a standalone on
>> my assistant's machine for my own cases at the moment!
>>
>>
>> --
>> Dr. Richard E. Hawkins, Esq.
>> (702) 508-8462
>> _______________________________________________
>> use-livecode mailing list
>> use-livecode at lists.runrev.com
>> Please visit this url to subscribe, unsubscribe and manage your
>> subscription preferences:
>> http://lists.runrev.com/mailman/listinfo/use-livecode
>>
>
>



More information about the use-livecode mailing list