Eric,

>From the Docs --

Unavailable commands

Codelock, Forms, List, Query, RBedit, Reports, Set (w/o keyword), 
express, Help, List Access, RBDefine, RBLabels, Rules, Trace, 
Show (except Show Error and Show Var)

I've used "alter table" for years under runtime, but that was not the 
command that was failing.

Thanks,

Ben



On 6 Feb 2002, at 10:51, Eric M. Bienstock, Ph.D. wrote:

> | Do you mean to say "alter table" is not supported by runtime?
> ==========================================
> 
> Ben,
> I haven't actually tried that command with a recent version of Runtime, but
> my recollection is that Runtime was not designed to support commands that
> alter the db structure.  Best if you check with RBTI on that.  Let us know.
> Regards,
> Eric
> 
> ---------------------------------------------------------------------------
> 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: Wednesday, February 06, 2002 2:29 AM
> Subject: Re: RunTime Problem
> 
> 
> | > I'm still not clear about an important point:  does the code work under
> | > regular R:BASE but not under Runtime?
> | >
> | Yes
> |
> | > Also, you say "it [the code] began a routine for a database
> modification."
> | > Does this mean you are trying to modify the database structure under
> | > Runtime?  Such commands are not supported by Runtime.
> | >
> | Do you mean to say "alter table" is not supported by runtime?
> |
> | > Also, you say "It [the code] is actually obsolete at this point."  If
> so,
> | > can you just delete the code and move on?
> | >
> | Yes I can and will. But these surprises are a very expensive
> | support issue.  This time I was lucky -- only one customer was
> | effected. Had it been deeper in the code I could well have installed
> | this at several sites, and cleaning up the mess would have been
> | significant.
> |
> | Ben Petersen
> |
> | ================================================
> | 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/

Reply via email to