Unload the WHOLE structure and text search for NUMBER (brute force method)

> -----Original Message-----
> From: [email protected] [mailto:[email protected]] On Behalf Of Doug
> Hamilton
> Sent: Wednesday, September 16, 2015 2:43 PM
> To: [email protected]
> Subject: [RBASE-L] - RE: Column-not-found anomaly
> 
> Bruce & Karen - thanks....but....
> I took out the #...and then decided just to remove the whole rule since
> there was a SELECT in it..and that rule is redundant for a PK column.
> Reloaded the db, still get the same errors (Column NUMBER not found and
> syntax err for SELECT command).
> Tried SET RULES OFF, still same errors.
> 
> Karen, there are no views in the db - tried a BRO ALL FROM SYS_VIEWS
> but it's an empty system table.
> 
> I recreated the form using the wizard and it works ok.  So I'll just
> fluff it up a little and everything will be ok.
> 
> Thanks again,
> Doug
> (But I'm still curious...)
> 
> 
> 
> On 9/16/2015 8:44 AM, Bruce A. Chitiea wrote:
> 
> 
>       Is the ' # ' character in the TABLENAME alias ' #T.1 ' a factor?
> 
>       Is the ' # ' character reserved for COLUMN NUMBER aliases?
> 
>       Bruce
> 
>       -----Original Message-----
>       From: [email protected] [mailto:[email protected]] On Behalf Of
> Doug Hamilton
>       Sent: Tuesday, September 15, 2015 7:06 PM
>       To: [email protected]
>       Subject: [RBASE-L] - Column-not-found anomaly
> 
>       Hi all -
>       I get an error when trying to run a form named CUSTOMER (main
> table
>       CUSTOMER):
>       R> edit using CUSTOMER
> 
>       The form displays with data and the following dialog:
>       -ERROR- Column NUMBER not found (2369)
>       The error actually appears twice, then I am in the form.
> 
>       Then when I tab to different fields, I get: -ERROR- Syntax is
> incorrect
>       for the command SELECT (2045)
> 
>       The form has only one table (CUSTOMER), with no EEPS in the form
> or on
>       the table; no Stored Procedures or triggers in the db.
> 
>       CUSTOMER table has a PK with a PK unique rule:
>       CustNumber IS NOT NULL AND CustNumber NOT IN ( SELECT CustNumber
> FROM
>       CUSTOMER #T1 WHERE #T1.CustNumber = CUSTOMER.CustNumber)
> 
>       There are no columns named NUMBER in the db, the closest one is
> CustNumber.
> 
>       The form runs ok when run from Form Designer.
> 
>       I've unloaded and deleted the form, reloaded the db, loaded the
> form and
>       reloaded the db to no avail.
> 
>       R:Base 9.5-32, Aug 6.
> 
>       Any clues for the blues?
> 
>       Thanks much,
>       Doug
> 
> 
> 
> 


Reply via email to