Executing the relayer command via a do statement fixed the problem. For my own eduction, I'd like to know a little more about the "as needed" compilation Richard mentioned. Does this happen every time a stack is opened, or only the first time a stack is opened on a different platform than it was compiled on?
Pete lcSQL Software <http://www.lcsql.com> Home of lcStackBrowser <http://www.lcsql.com/lcstackbrowser.html> and SQLiteAdmin <http://www.lcsql.com/sqliteadmin.html> On Thu, Mar 13, 2014 at 10:26 PM, Peter Haworth <[email protected]> wrote: > You're right, that's strange. The first mention I can find of it in > either the dictionary or the release notes is 6.0(DP1). > > I think you may have solved the mystery though. I do see relayer in the > commandnames in 5.5.4 on OSX but it's not there on 5.5.0 on Windows which > is where I see the problem, and it's not in the commandnames in that > version. > > The line that the error is flagged does have a reserved word (before) in > it, maybe the compiler thinks there should be a comma separating it from > the other parameters? > > I wonder if I can get round this by using a do statement instead of > executing the command directly within the script. I will try that and post > the results. > > Thanks for the lead Mark! > > > > Pete > lcSQL Software <http://www.lcsql.com> > Home of lcStackBrowser <http://www.lcsql.com/lcstackbrowser.html> and > SQLiteAdmin <http://www.lcsql.com/sqliteadmin.html> > > > On Thu, Mar 13, 2014 at 7:32 PM, Mark Wieder <[email protected]>wrote: > >> Pete- >> >> Thursday, March 13, 2014, 6:29:11 PM, you wrote: >> >> > As mentioned, it compiles fine on OSX under 5.5.4 even though the >> relayer >> > command doesn't exist in that version. >> >> Actually, it does. Type this in the messagebox: >> >> put "relayer" is among the lines of the commandnames >> >> -- >> -Mark Wieder >> [email protected] >> >> This communication may be unlawfully collected and stored by the National >> Security Agency (NSA) in secret. The parties to this email do not >> consent to the retrieving or storing of this communication and any >> related metadata, as well as printing, copying, re-transmitting, >> disseminating, or otherwise using it. If you believe you have received >> this communication in error, please delete it immediately. >> >> >> _______________________________________________ >> use-livecode mailing list >> [email protected] >> Please visit this url to subscribe, unsubscribe and manage your >> subscription preferences: >> http://lists.runrev.com/mailman/listinfo/use-livecode >> > > _______________________________________________ use-livecode mailing list [email protected] Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
