Is "Status" a protected word now???

[John Esak]

> John Esak wrote:
> >
> > Is the word "Status" protected now??? Maybe something in ODBC.
> Lots of my
> > code will break...
> [...]
> > I use something like this all the time... why is it breaking now?
> [...]
>
> There is a STATUS object in filePro 5.0, so that's what is causing the
> problem.  However, it's been there for over 3 years, so I don't know why
> you just ran into it.

How do you know I just ran into it??  I'm just telling you about it now...
maybe before I just walked into it and it didn't hurt as much then... :-)

I looked at all my old code... and somewhere along the line, I actually
changed the fieldname Status for status_1, and added status_2, etc., as I
intutively "sensed" that you would be adding a Status object one day... :-)

Is that for the BREAK, ESCAPE, CURSOR stuff??

John

P.S. - And just for grins... I was not able to find any _other_
unexplainable protected word.  Status seems to be the only one, correct? In
other words, what other particular word would cause this same problem... and
why? Aren't the "object" names somewhere in the precedence list of all the
other keywords, like fieldnames, labels, aliases, selection sets, etc.,
etc.? Meaning, it's hard to make any other conflicts show up, why just this
one?