Technically your approach is doable. For me the better ways would be to have working CA classes for both data sources available and use some dynamic factory mechanism to decide which is loaded - could also be some config file aproach. You could code a static class hierarchy and modify the loaded CA properties in .init(), but I think statically filed property values will give a more stable environment - esp. if you code with them from the command window as well.

But I'd start working with the new backend in place first. If the rewritten app does not offer dbf datasources, you will have the correct environment to observe any areas in need of optimization/further interest right from start. Even if the converted app gives freedom to use dbf, having a well tested migration path from dbf2SQL will be nice if your customers are offered it ;-)

Having to confront data type issues - if any exist for targeted back ends - very early on is a benefit in my eyes as well.

BTW and totally off-topic: I have (mis-)read twice your company name as WTF Data Services. Perhaps your initials (guess...) invite that ;-)

rgds

thomas

>Hi,
>
>Just learning how to convert my dbf app to a client server. It's a re-write....I would like to use a cursoradapter with native dbfs for testing. After I am satisfied, i would like to now connect to the sql server. I would have already created the structures on sql server. The remote views has a localtoRemote property to make it easy to switch. How can I do that with a cursoradapter? (Using Promatrix Framework)
>
>Thanks,
>
>Bill