Do you condifer it a drawback that the code for the procedures is stored in the
database?

If you wanted to convert the data to VFP or Oracle, or some other DB, wouldn't you
then have to convert all the SP's with it?

Thanks



>Stored procedures are generally more secure and have better performance.
>
>>I'm soliciting opinions on which is the better design:
>>
>>Create a class that acts as a tier that has methods to return all the types of data I need, such as
>>'GetCustomersByState()'. This class would have the responsibility of knowing
>>the data store.
>>
>>I could then call into this class and get back any data I need. Switching from VFP to SQL to Oracle
>>would only entail modifying this class to match changes in structure on the new DB.
>>
>>The other option is to create stored procedures for each set of data I might need. Problem here is that
>>the stored procs would need to be converted to work with the target database.
>>
>>Inquiring minds wanna know.