>You could have a dynamically constructed RV (it is, after all, an SQL Statement) that builds the SQL statement and then makes the call to CREATE SQL VIEW REMOTE blah blah AS
based on the criteria that the user enters. This method does not require any changing of code on the client and I found it quite effective for the query tool-generated picklists in an app I previously worked on.
The caveat here is that you have to be careful to "clean up the mess" afterwards. Unless you are using a temporary DBC, dropping and recreating views will lead to DBC bloat. This could be a problem if the user count is high and they are sharing the same installation. Less of a problem if all clients have their own copy, but still an issue.
Dan LeClair
www.cyberwombat.comSET RANT ON - The Wombat BlogLife isn’t a morality contest and purity makes a poor shield. - J. Peter MulhernDisclaimer: The comments made here are only my OPINIONS on various aspects of VFP, SQL Server, VS.NET, systems development, or life in general, and my OPINIONS should not be construed to be the authoritative word on any subject. No warranties or degrees of veracity are expressed or implied. Void where prohibited. Side effects may included dizziness, spontaneous combustion, or unexplainable cravings for dark beer. Wash with like colors only, serve immediately for best flavor.
