Kevin,

Thanks. I agree that is probably a better development method. I'm OK with SP's.. but not an expert.. I think that as I gain proficiency with them I will start to do more and more.

I definitely agree about the unit testing. When I build up a big string for sql inside fox, and then run it, if it blows up it's hard to figure out where. If I put it in QA, QA is very smart about telling me what and where my code blew up. Until I get more proficient with T-SQL, in the meantime, I do this..
_cliptext=lcsqlmd
suspend

Then paste my sqlstatement into QA and run it.

>David,
>
>At one time I had those same concerns, but I don't any longer. You can use scripting to generate the stored procs. I find it easier to unit test sql code when it's used as stored procs, rather than inside a fox component.
>
>Kevin