filePro to SQL

[Bill Campbell]

On Thu, Apr 23, 2009, Ryan Powers wrote:
>> Track field names as used, then add index numbers to the end?
>> 
>> some_field
>> some_field2
>> some_field3
>> [etc.]
>
>Exactly.
>
>> In your defense, I think maintaining the edits is a complete waste of
>> time.
>> I see edits as an application-level function, not a storage-level
>> function.
>
>The issue really is that filePro edits are dual purpose. If they were
>strictly field types it wouldn't be much of a problem, but as you say, they
>are also used at the application level which muddles things quite a bit and
>(I could be wrong here) is the primary reason that they are lenient as field
>types.

Filepro edits can get in the way when loading data that one knows
is clean (as can stored procedures and/or triggers on postgresql
or other SQL databases).  It's been a long time since I did bulk
loads of data into FilePro, but I seem to remember disabling
edits during loads, and enabling them when done.

Things like putting spaces or non-alphanumeric characters in
field names or file names belong in the category of DON'T DO
THAT!!!!  While one can enclose field names in quotes on some SQL
databases, it's a PITA, and causes far more problems than it's
worth.

Bill
-- 
INTERNET:   bill at celestial.com  Bill Campbell; Celestial Software LLC
URL: http://www.celestial.com/  PO Box 820; 6641 E. Mercer Way
Voice:          (206) 236-1676  Mercer Island, WA 98040-0820
Fax:            (206) 232-9186  Skype: jwccsllc (206) 855-5792

There is no distinctly native American criminal class save Congress
    -- Mark Twain