Many AREV generations ago, I created a symbolic field called REAL in many of the tables in a database. This field examined information for each record and determined whether it contained actual data, or was a "fake" record used for demonstration and training. Most queries were written to select records "with real eq 1". This continued to work even when AREV implemented SQL and at some point, REAL was reserved. I would get the message that REAL was a reserved label if I tried to create a new field called REAL, but the old ones still worked. Now, mysteriously, the old ones no longer work and I get error messages on all those queries. I'm sure I should ferret out all the problemmatic code and change it, and probably I should get rid of the whole idea of "fake" records, since it slows down my queries, but I'm curious as to why this would suddenly change.

It sounds like a symbolic recompilation has occurred at some stage, perhaps when you first attached AREV 3.x to the older volumes. This would effectively modify their behaviour. If I recall a system message accompanies this recompilation.

I think you have little choice but to recompile new symbolics with a different KEY (perhaps "UNREAL" )

Steve

Thanks. (I went with ACTUAL–didn't want to cope with users having to deal with NOT UNREAL logic!)

View this thread on the forum...