Have you thought about creating two data layers, one for SQL Server and one for Oracle? As long as they both provide the same interface, you should be able to user either based on a configuration parameter.

The benefit of this, IMO, is that you can write code that is optimized for the data store that will be accessed.

-Mike

>Thanks, Mike. That looks like it might be a great help to us.
>
>Our app has approximately a dozen different triggers and about two dozen stored procs. Currently we're only supporting SQL Server 2000, but we'll have a requirement next year to support Oracle. Because of this, we want to ensure that every line of back-end code will run in Oracle (or DB2, etc....thus the interest in conforming to ANSI-92.)
>
>Kevin