On Thu, Sep 11, 2014 at 3:02 PM, Gene Wirchenko <[email protected]> wrote:
> At 09:35 2014-09-10, Bill Anderson <[email protected]> wrote: > >> (NapTime) >> >> I did some research on this...after all, this vital detail was somehow >> missed by all the Hacker's Guide books... >> > > Gasp! No! > Hard as it is to believe, there were things deep inside the language even we did not tease out. I wonder if NAPTIME is a dBASE-compatible thing; there were a couple of 'reserved' keywords that were on the list just because they were a dBASE or Clipper term, and the Fox Team wanted to avoid hard to chase down incompatible behaviors. A quick web search yields no clues. > > At one point, I had a table with a column called "status". > Everything was going fine until I wanted to check the value in one row and > typed list or display status. I did not get what I was expecting. I > changed the column name. > Table and field names can be real problems. I've run into errors while porting "APPEND and REPLACE" systems into SQL statements. Apparently, the xBase parser could work out the difference between keywords and fieldnames, but the SQL parser was more finicky. -- Ted Roche Ted Roche & Associates, LLC http://www.tedroche.com --- StripMime Report -- processed MIME parts --- multipart/alternative text/plain (text body -- kept) text/html --- _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/CACW6n4u6OZDVGvFR=xwhrkvta7uf7awvcsgnxp+enw_wwf4...@mail.gmail.com ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
