I'm converting a DBC to SQL using DDT...first time - so - having lots of questions!!!



What do you guys do with the default values? Do you enter them in the DDT and have that stored in the SQL database - or - is it best to leave that blank?



Also, what's best choice with regard to default values for primary keys and foreign keys - (-1 or 0)?



Lastly, what's the best way to get the data from VFP to SQL? Is there something in DDT that does that - or - am I on my own to write that code?



I figured some of you have already done this and would be able to help with some "gotchas" and things to avoid. Any help is greatly appreciated!



HB

All my VFP stuff used GUID pks and I was originally drawn to Full Convert because unlike the "upsizer" it would let me map my GUIDs to UIDs. I never used autoinc integers in VFP databases.



Most of my VFP -> conversion was done for other peoples apps as I started developing VFP apps exclusively against SQL starting about 2002.



I usually found that RI ( especially straight VFP RI without Steve Sawyer's brilliant mod ) wasn't something I wanted to even think about converting so I just moved the table data and set up the RI triggers where appropriate in SQL itself after the data was moved.



When on the Table Setting screen I would only check Recreate Data ( having already created the structure I wanted with DDT ) and then check Skip Indexes and Skip Constraints.



I found it was better to move the data from VFP to SQL without indexes or RI or defaults - ie. data only - no metadata - and then set things up in sql the way I wanted it. I don't trust any "automatic" conversion of that kind of stuff as I always assumed ( perhaps incorrectly ) that the VFP implementation of some of that stuff may have been done to look like SQL it really was different ( RI being a good example )



Full Convert's primary utility for me was in mapping the fields and doing the actual data transfer and storing those setting in projects so they were reproducable and tweakable. I found the VFPOLEDB driver flakey or I would have done it from the SQL side with DDT / SSIS.