The end consumer will be a webpage or thick client. i am trying to find a way to easily change from one database to another. oh, and it doesn't have to use ado.net, it can convert the cursor into xml or a string for all i care as long as it doesn't slow it down to much.
i guess my main question is, is using the cursoradapter a viable means for developing a data layer that needs to be able to point to different databases (not necessarily a mix for each build though, just if a client prefers we use sql server or whatever, instead of vfp)

>Hi,
>
>>>
>i am a little confused about creating a data layer mtdll designed for use with multiple databases (foxpro, oracle and sql server).
>cursoradapters seemed like an ideal solution to retrieve all the data i needed using the foxpro code i am familiar with, but then i read that the cursor can't be passed to different layers unless converted to XML or an ado recordset.
>my issue is, how much of an overhead is this? wouldn't it make more sense just to use ado.net with vfp8? or are there hidden issues with using ado.net that i am unaware of?
>>>
>
>What's going to be the end consumer of this data? I'd certainly question the efficiency of using VFP as a middle layer to get MSSQL or Oracle data into ADO.NET...
>
>Regards,
>Viv