I third the motion. I almost always use GENDBC generated code as part of the script and I should have mentioned this in my original reply. Good one.


>>If you chose to write a script file (that's how we do it), you can get a pretty good jumpstart with GENDBC.prg in your HOME() + "tools/gendbc" directory.
>>
>>Be careful to modify it though, it wants to recreate all the tables as well.
>>
>>M.
>
>
>I also use the gendbc as explained above. What I do is create another .exe file (usually called patch#.exe or something of that sort.) Gendbc in vfp 6 is better because it breaks each view/table into a function call. My patch only contains the functions I need. Normally I will check for the existance of the view or table before I run it - no sense in asking for trouble. If it doesn't exist or is modified, I will delete the view the recreate it. Next I check to see if it was built correctly. I've been doing this for quite some time and it has worked well for me.
>
>Robert