Re: 4GL variable substitution in SQL statements - a feature request

Peter Lancashire wrote: > > Having been bitten by this one several times recently I thought I would > ask if anyone else finds it a problem. [SNIP] > The current system makes it tricky to use variable names that are the > same as column names unless the column names are qualified with a table > name or given the @ prefix. [SNIP] This is the reason most of us just avoid using column and table names as 4GL variable names without either prefixing them (like p_column for "program variable" or g_/s_/l_ for Global/Static/Local etc) or placing the variables into a structure so that the structure.field syntax makes it clear to the compiler and read both that this is a program variable. The real solution here is coding discipline. Art S. Kagel