>>Hi
>>
>>I've been looking at VB.Net over the last few days, and my first little tasks were to try a few data routines.
>>
>>Is it me, or have we been spoilt with FoxPro, here are my initial impressions whilst creating/running a program to process some information on some FOX DBF's:
>>
>>

I have to write at least 5-times as much code as I did in VFP
>----
>Yes - that is by design. and it was inherited behavior from VB 6 - takes as much code there too to get to data in VB.NET, ASP.NET and ANYTHING dot net-able. It's a sad sad sign that no matter how efficient I make my code - I must run it on mondo FAST processors. However - my speed tests with record retrieval and insert with C# vs VB.NET are meaningful to me - perhaps you should go to C# and forget about VB.NET for a while?

Unfortunately I cannot switch to C#, we HAVE to go with VB.

>>

It's so sloooooow, what takes 15 seconds in Fox, takes over a minute in VB.Net - which will mainly be due to using the OLE DB provider, which I can understand, but still, it is rather a dip in performance
>----
>O O - have u tried a record insert or record update yet?? You think you've lost hair recently to 'get' the data - now lose some more watching it 'put' the data back to the data store.
>---

Yes, getting the data wasn't too bad, but putting it back takes around 1 minute, that is absolutely pathetic IMO, it's only 2,500 records, on my Harddisk!!! 919kb?? It takes 1 minute to write 919kb's worth of data!

Kev

>>
>>Like I said, I can understand WHY it has to be this way, but I do feel cheated having being made available to some brilliant DB commands in fox, only to have to be brought back down to reality with a different product.
>>
>>Otherwise, excellent product, as far as I've used it.
>>
>>Anyone else feel this?
>>
>>Kev