Thanks Cindy & Craig


>>...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. ....
>>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.
>
>Hi Kevin,
>
>Beyond what Craig said about stored procedures, you can still use a data class as a traffic cop. In case the stored procedures were somehow different from one back-end to another your user interface will still be interacting with the data class and anything behind that would be transparent. I have no idea how performance would be, but it might be easier to program and maintain.