David,
The sort answer is Yes. You really want to change all column names to not
use special/illegal chacraters. I had many also with # and "." A recall a
column named "tk.des#" which work in some instances but not others. RCode
and Rstyle do a great job in locating correcting these names.
Good Luck. You'll be glad to get this behind you.
Dennis
****
>Getting ready to receive a legacy upgrade to 6.5++, I'm giving my code a
spring clean and switching to the new / upgraded commands already published.
>
>I started way back with System V and needed unique column names for Client
Number, Contact Number and so on. The documentation gave no warnings
against and so I adopted Cli#, Cn#, Tm#, Emp# as easily identifiable
linking column names.
>
>Since then, we haven't had a problem which seemed to directly relate to
this, although our DB is small compared to some I see on the list.
>
>I generally work on the 'if it aint broke...' principal, but are there
valid reasons why I should change from CLI# to say CLID and so on ?
>
>Command files would be easy. ClipMate5 (a really useful util) will search
out a column name and change every occurance in every command file with a
single command and would take under 10 minutes to go through the lot.
>
>View definitions are also in command files (thank you Dennis McGrath and
others) so their definitions would also be changed during the above.
However LOB files (Forms and Reports) would be very time intensive unless
there is a shortcut.
>
>The wisdom which comes down from you Learned Wizards is a great help when
you work alone. Any advice or LOB shortcuts would be appreciated.
>
>David Atkinson.
>[EMAIL PROTECTED]
>www.skidbusters.co.uk
>
At 08:32 AM 6/1/01 +0100, you wrote:
Getting ready to receive a legacy upgrade to 6.5++, I'm giving my code a
spring clean and switching to the new / upgraded commands already published.
I started way back with System V and needed unique column names for Client
Number, Contact Number and so on. The documentation gave no warnings
against and so I adopted Cli#, Cn#, Tm#, Emp# as easily identifiable
linking column names.
Since then, we haven't had a problem which seemed to directly relate to
this, although our DB is small compared to some I see on the list.
I generally work on the 'if it aint broke...' principal, but are there
valid reasons why I should change from CLI# to say CLID and so on ?
Command files would be easy. ClipMate5 (a really useful util) will search
out a column name and change every occurance in every command file with a
single command and would take under 10 minutes to go through the lot.
View definitions are also in command files (thank you Dennis McGrath and
others) so their definitions would also be changed during the above.
However LOB files (Forms and Reports) would be very time intensive unless
there is a shortcut.
The wisdom which comes down from you Learned Wizards is a great help when
you work alone. Any advice or LOB shortcuts would be appreciated.
David Atkinson.
[EMAIL PROTECTED]
www.skidbusters.co.uk
Dennis Fleming
IISCO
http://www.TheBestCMMS.com
