BOb,

>Any thoughts of sharing your VFP 'generators'? Perhaps it would make a good article in CODE mag, about how you used VFP as a dev tool for .Net stuff.<

Well, no one's asked me to do an article in CODE magazine yet, but I've already been asked about writing one for the UT magazine (about typed DataSets). I don't have the time right now to do much of anything ... major deadline coming up in a coupla weeks that I can't miss. Maybe after that, I'll think about writing stuff and/or sharing some of our VFP code generating ideas.

~~Bonnie


>I actualy have a set of SP's that do this for me. We don't have one that goes through ALL of the tables, but with little work it could be modified to do that. We got them from an article in pinnicles SQL mag and tweaked them somewhat to format the way we prefered them.
>
>Any thoughts of sharing your VFP 'generators'? Perhaps it would make a good article in CODE mag, about how you used VFP as a dev tool for .Net stuff.
>
>BOb
>
>
>>Right ... but you have to do it for each table yourself. You can write a VFP prg to automatically go through every table in the database and spit out the T-SQL for every table.
>>
>>~~Bonnie
>>
>>>The Query Analyzer can do a lot of that for you. Open the Object Browser (F8), drill down to a table of interest and right-click on the table. Select one of the Script Object... options.
>>>
>>>-Mike
>>>
>>>>We just wrote a little VFP prg that can take a table from SQL, get all the column names, and generate all the T-SQL commands to the clipboard which you can then paste into Query Analyzer, tweak where necessary and then run in Query Analyzer to create the SP. (We then save all the generated SPs into .sql files, so we can automate the process of recreating the SPs when we need to). If you make a few assumptions about naming conventions (such as having your PKs named the same as your table ... so the PK for Customer would be CustomerKey) ... then all the basic SPs (select/delete/update) need no tweaking at all. IN fact, we skip the "pasting them into Query Analyzer" step and have the VFP .prg just save them to a .sql file and run them against the database directly from VFP to create the SPs (using SQLDMO). The tweaking in Query Analyzer is only necessary for the custom SPs, that do more.
>>>>
>>>>Food for thought ...
>>>>
>>>>~~Bonnie