>Since he threw in tables and data after the original question, this is no longer totally true. He will have to modify the code for any table structure that changes. He will only be able to ALTER TABLE if there is to be no data loss or any other RI/indexing/PK loss.

Couldn't these still be done by modifying the code? Data loss would only occur if I delete fields, and RI/indexing/PK loss only if I modify fields that are part of that? Couldn't I modify the appropriate code to handle this also anyway? BTW, this has now become more for my understanding of how this works than for any current practical application, but it still important for me to know (see comment below)...

>
>I know SDT seems expensive for some, but when compared to how many billable hours it would have taken me to roll my own, SDT paid for itself with the deployment of my first VFP app. I rolled the cost of SDT into my first app. Now, SDT is virtually free in all my other apps. I also got a 10% discount because I was a PUTM.

I have heard nothing but great things about this toolkit. I'm going to go ahead and get it. I didn't see anything at their site about a PUTM discount; think it's still available?