>I grant you that it is simple. That said, dynamic pl/sql allows you to do the same thing - in a more secure/scaleable environment. I agree that client-side rendered sql *can* be a good idea. The most notable drawback in Mark's approach is that it is Fox-Specific. This may or may not be an issue. If given the choice between two options - and one may be require a little extra effort - but it is platform neutral, I will go with that option.

The code is Fox specific, but the SQL it generates is not. However, the SQL is specific to Oracle syntax if that is what you mean. Since SQL Server, MySQL or any other SQL DB is not even on our radar screen where I work, this is a non-issue for me. Anyway, I take a mixture of approaches - ad-hoc SQL generation, RVs, data classes from the client/app, and SPs, Packages, triggers, views, etc., on the server. Just depends on what I need.

As for the extra effort, I have a VFP PRG that will query an Oracle schema and generate SQL script files that I then can tweek and use to create the packages, procs, etc., on the server. You can also do this to create a list of SQLEXEC() commands to call the procs that can be pasted in your apps. Not much effort there on my part, just let VFP do the work for me. < bg >

I also use SQL to generate [spool] SQL script files. I don't think a lot of developers realize how powerful of a tool SQL is and how much time it can save you if only they would take a SQL Intro course or read an intro book.