>Alejandro,
>
>It sounds as if you want a tiered approach, with a VFP app handling the data and passing it to a NET front end?
>
>If that's the case, it's not really a data repository issue at all, it's more a data transfer issue.
>
>Are you able to tell us more about your goal? IMHO these sorts of cases are very useful, especially if you keep us informed as you go along.

Thank you very much for your answer, John. You described the issue better than I did. The reason I started off talking about using OleDb is because Strataframe, the NET framework I am using (Ivan uses it also), has a built in mechanism to use it as the datasource.

As data is entered in this (time and attendance) application a lot of recalculations are made to provide feedback of overall results up to that point. The recalculations include consulting this and previous transactions. We did something similar in our payroll (VFP) app, so we have experience and code that applies and it uses SQL SELECT intensively. Besides the fact that the history in the payroll app is in DBFs, and granting that there are other ways of doing it, I simply am not ready to give up VFP and the knowledge I have.

So why use .NET at all? For us this is natural point to start mastering the tools in which MS is betting the company. Unless Strataframe disappoints, which I don't think it will, the path is set. Perhaps I am rationalizing, but I'd like to become proficient at combining VFP and .NET.

Thanks for the feedback. I look forward to more.

Alex