Re: # in column names

[Michael Young]

Hi David,

Tango/HTML has a lot of problems with # in column names. If you are going to do any web based access then my advice is to change them. The biggest problem is finding every instance in the Windows version in forms and reports which you are aware of. It was easy to do in DOS versions. I too would like to find some easy way to do this in Windows. If only there was some shortcut like either a search utility or perhaps when a column gets renamed it will also do the variable definitions in forms and reports/labels. This would be a gigantic enhancement that I am sure EVERYONE would love.

Best regards,
Mike Young

--Original Message Text---
From: David Atkinson
Date: Fri, 1 Jun 2001 08:32:19 +0100

 
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#,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, butthere valid reasons why I shouldfrom CLI# to sayand so on ?
 
Command files would be easy. ClipMate5 (a really usefulwill search out a column name and change every occurance in every command file with a single command andtake 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. advice or LOB shortcuts would be appreciated.

 
David Atkinson.
[EMAIL PROTECTED]
www.skidbusters.co.uk