UPSIZING Wizard can error due to field name

[jrumbaug]

I just hacked out why I could not upsize a table with the UPSIZING wizard in VFP8. I thought it was NUL date values causing the problems. No, it was a field name. A field was named CURRENT to hold the dollar value currently due. After renaming the field to NOWCURRENT, I can upsize it with no errors.

I hope this may help you in the future.

Jim Rumbaugh

 

[Mike Lewis]

Jim,

You've raised a good point. SQL Server is much stricter than VFP in using reserved words as field names. The upsizing wizard will often choke on field names that happen to be reserved words, even if VFP allows them.

Mike


__________________________________
Mike Lewis (Edinburgh, Scotland)

My sites:
Visual FoxPro (www.ml-consult.demon.co.uk)
Crystal Reports (www.ml-crystal.com)

 

[Neil Toulouse]

...and following on from what Mike said, reserved words can be used in SQL Server as field names, but you have to add square brackets around them (eg [CURRENT]).

Unfortunately, you can't change the field names in the upsizing wizard so it doesn't really help!

I like work. It fascinates me. I can sit and look at it for hours...