Thanks for the info
I'll check this.

But what about local data engine? I know that, as solutions,Foxpro OLE DB or MSDE is often suggested, but why not to have the engine in NET and do nice things like indexed incremental searching in thousands items lists without having to load too much in memory?
Why VistaDB.NET, TurboDB.NET, CodeBase.NET and not VFoxpro.NET ? I mean as local data engines.
Seeing one Ken message in this thread, I think that something will be done in this direction, though, for the next VS.NET version.
"Many Visual FoxPro features from language, to data, to tools, are being added to upcoming versions of Visual Studio"
I'm very curious what this means.



>>Just think at the equivalent in C# of those simple commands with parameters:
>>
>>

>>conH = SQLSTRINGCONNECT({connection_string})
>>SQLPREPARE(conH , [select * from {some_table} where some_column IN (?param1, ?param2,?param3,?param4)])
>>...parameters asignments
>>SQLEXECUTE(conH)
>>BROWSE
>>

>
>You can use code pretty similar to this if you use the VFP toolkit.
>
>BOb