Mark,

>I believe this is called the Upsizing Wizard < g >. Seriously, there are so many differences between SQL Server and Oracle and other SQL DBs that I don't think this is very practical. Conversely, I can design and develop an Oracle DB [just as someone else can do the same in SQL Server] where you can achieve a very high degree of front-end independence.

I understand your point, but the whole topic of HOW to design for multiple backends is very relevant for many people. I have a developer client right now who needs to develop a strategy for targeting Oracle, SQL Server, and perhaps more, in addition to VFP tables. Someone who has done that could share the war stories and trade-offs involved and produce a very interesting session, I think.

However, I'd sure love to hear you speak strictly about the Oracle issues, if that's where your experience is.

>Even products like DataClas 2000/COM can't really achieve backend independence. Rod is developing separate Oracle classes and wizards where the SQL Server product has been shipping for months [a year?].

By separate classes, you mean separate data access classes, which can work with the same middle tier, or a completely separate version of the entire framework? I understand that the wizards might need to completely different, since DataClas depends on Stored Procs so heavily.

>I am really interested in brutal honesty about my original post regarding DevConnections topics on Practical VFP and Oracle.

I encourage you to submit a proposal for Oracle-related topics, including one on the differences between SQL Server and Oracle syntax, etc., which would at least hint at this area we've been discussing.