Hi Ben, I normally use "in" preceding a sub-select...
One of the other Ben's ;-) ----- Original Message ----- From: "Ben Petersen" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, February 05, 2002 11:58 AM Subject: Re: RunTime Problem > Eric, > > I found the code segment that is the problem. It is actually > obsolete at this point, it began a routine for a database > modification. Has been included in the app since 8/24/2000 > according to my notes. I ran it against 3 other databases with > identical schemas used by other customers with the same results. > > Sel count(sys_column_name) into zCt + > from sys_columns + > whe sys_Column_Name = 'I' + > and Sys_Table_ID = + > (sel Sys_table_ID fro sys_Tables + > whe Sys_Table_Name = 'DuesSched') > > > Ben Petersen > > On 5 Feb 2002, at 21:44, Eric M. Bienstock, Ph.D. wrote: > > > |.... There are no commands in these files that are _explicitly_ not > > | supported under runtime, and as best as I can tell it's crashing in > > | an early part of the app (prior to the first menu) .................. > > ========================================== > > > > Ben, > > Post the code here. > > > > -------------------------------------------------------------------------- - > > Eric M. Bienstock, Ph.D. > > Database Development, etc. > > Authorized R:BASE Developer > > Eric M. Bienstock & Associates, Inc. > > day: 212-978-7948 eve: 973-763-8650(8) > > FAX: 209-882-9250 [EMAIL PROTECTED] > > http://members.home.net/ericmb/Ericmb.htm > > -------------------------------------------------------------------------- - > > > > ----- Original Message ----- > > From: "Ben Petersen" <[EMAIL PROTECTED]> > > To: <[EMAIL PROTECTED]> > > Sent: Tuesday, February 05, 2002 12:52 PM > > Subject: Re: RunTime Problem > > > > > > | Eric, > > | > > | The customer is running RTW 6.5+... I mistakenly sent files > > | codelocked under 6.1a the first time, did the slap-my-forehead-with- > > | heal-of-hand thing <g> and sent again codelocked under 6.5+, to > > | no avail. I use RClass to assemble my command files for > > | codelocking, and it automatically deletes previous apx files. As > > | well, I have it set to strip comments from command files before it > > | generates the APP files. > > | > > | > If it runs under regular R:BASE but crashes under Runtime, > > | > then the fault is probably some command that Runtime does > > | > not support. > > | > > | There are no commands in these files that are _explicitly_ not > > | supported under runtime, and as best as I can tell it's crashing in > > | an early part of the app (prior to the first menu) which has been > > | running under runtime for a couple years now. As well, it runs fine if > > | traced under runtime. > > | > > | Thanks, > > | > > | Ben > > | > > | > > | On 5 Feb 2002, at 20:12, Eric M. Bienstock, Ph.D. wrote: > > | > > | > |... I codelocked an application today, sent it to a > > | > | customer, and got an exception error upon starting it up... > > | > ========================================== > > | > > > | > Ben, > > | > > > | > I've always found that it's important to Codelock with the same version > > you > > | > plan to run the APX. Also, be sure to delete the previous APX prior to > > | > creating a new one. > > | > > > | > If it runs under regular R:BASE but crashes under Runtime, then the > > fault is > > | > probably some command that Runtime does not support. > > | > > > | > > > -------------------------------------------------------------------------- > > - > > | > Eric M. Bienstock, Ph.D. > > | > Database Development, etc. > > | > Authorized R:BASE Developer > > | > Eric M. Bienstock & Associates, Inc. > > | > day: 212-978-7948 eve: 973-763-8650(8) > > | > FAX: 209-882-9250 [EMAIL PROTECTED] > > | > http://members.home.net/ericmb/Ericmb.htm > > | > > > -------------------------------------------------------------------------- > > - > > | > > > | > ----- Original Message ----- > > | > From: "Ben Petersen" <[EMAIL PROTECTED]> > > | > To: <[EMAIL PROTECTED]> > > | > Sent: Tuesday, February 05, 2002 11:49 AM > > | > Subject: RunTime Problem > > | > > > | > > > | > | Hi all, > > | > | > > | > | I'm stuck. I codelocked an application today, sent it to a > > | > | customer, and got an exception error upon starting it up. Tried it on > > | > | my desktop under runtime (RBW6.5+) and got the same result. > > | > | They are running Win98 and I'm using NT4 server. > > | > | > > | > | I tried codelocking under both 6.1a and 6.5+ with the same result. > > | > | Runs fine under single-user and if I trace under Runtime. The odd > > | > | part is that the changes made between versions of the app are > > | > | fairly deep in the app, and this is crashing, it appears, right after > > | > | connecting to the DB. > > | > | > > | > | I'm a little desperate as several customers are waiting for this > > | > | update... any suggestions would be very much appreciated. > > | > | > > | > | tia, > > | > | > > | > | Ben > > | > | ================================================ > > | > | TO SEE MESSAGE POSTING GUIDELINES: > > | > | Send a plain text email to [EMAIL PROTECTED] > > | > | In the message body, put just two words: INTRO rbase-l > > | > | ================================================ > > | > | TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED] > > | > | In the message body, put just two words: UNSUBSCRIBE rbase-l > > | > | ================================================ > > | > | TO SEARCH ARCHIVES: > > | > | http://www.mail-archive.com/rbase-l%40sonetmail.com/ > > | > > > | > > > | > ================================================ > > | > TO SEE MESSAGE POSTING GUIDELINES: > > | > Send a plain text email to [EMAIL PROTECTED] > > | > In the message body, put just two words: INTRO rbase-l > > | > ================================================ > > | > TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED] > > | > In the message body, put just two words: UNSUBSCRIBE rbase-l > > | > ================================================ > > | > TO SEARCH ARCHIVES: > > | > http://www.mail-archive.com/rbase-l%40sonetmail.com/ > > | > > > | > > | > > | ================================================ > > | TO SEE MESSAGE POSTING GUIDELINES: > > | Send a plain text email to [EMAIL PROTECTED] > > | In the message body, put just two words: INTRO rbase-l > > | ================================================ > > | TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED] > > | In the message body, put just two words: UNSUBSCRIBE rbase-l > > | ================================================ > > | TO SEARCH ARCHIVES: > > | http://www.mail-archive.com/rbase-l%40sonetmail.com/ > > > > ================================================ > > TO SEE MESSAGE POSTING GUIDELINES: > > Send a plain text email to [EMAIL PROTECTED] > > In the message body, put just two words: INTRO rbase-l > > ================================================ > > TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED] > > In the message body, put just two words: UNSUBSCRIBE rbase-l > > ================================================ > > TO SEARCH ARCHIVES: > > http://www.mail-archive.com/rbase-l%40sonetmail.com/ > > > > > ================================================ > TO SEE MESSAGE POSTING GUIDELINES: > Send a plain text email to [EMAIL PROTECTED] > In the message body, put just two words: INTRO rbase-l > ================================================ > TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED] > In the message body, put just two words: UNSUBSCRIBE rbase-l > ================================================ > TO SEARCH ARCHIVES: > http://www.mail-archive.com/rbase-l%40sonetmail.com/ > > ================================================ TO SEE MESSAGE POSTING GUIDELINES: Send a plain text email to [EMAIL PROTECTED] In the message body, put just two words: INTRO rbase-l ================================================ TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED] In the message body, put just two words: UNSUBSCRIBE rbase-l ================================================ TO SEARCH ARCHIVES: http://www.mail-archive.com/rbase-l%40sonetmail.com/
