Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
VFP Definitely alive until 2010?
Message
From
16/09/2004 10:43:49
Walter Meester
HoogkarspelNetherlands
 
General information
Forum:
Visual FoxPro
Category:
Coding, syntax & commands
Miscellaneous
Thread ID:
00942119
Message ID:
00942916
Views:
30
Hi gerard,

>I think 'Any' application will need a grid (or whatever its called in other Laguages) and I think its a serious concern if speed is goint to be 5 times slower for doing a 'Basic' operation in any database system

As beeing said in this thread, I don't think you can draw that conclusion. Much depends on your strategy. In .NET handling large resultset is not as efficient in VFP in many ways, therefore the challenge is to cope with smaller resultsset and beeing smart. Only query data you need.

In .NET there is no equivalent to USE MyTable and THISFORM.Grid.RecordSource = MyTable. You'll have to do with ADO.NET which is not designed for handling large datasets. So trick is to only retrieve the data when you need it.

For most applications this won't be a big problem, but sometimes you need to handle large resultsets (e.g. munging data into a lengthy report). Then you most likely would see the difference in performance.

That beeing said. I don't think there is a general rule saing that handling data is x times slower than in VFP. It really depends on how you do it. When comparing a native VFP database application with a .NET SQL/Server applications, the odds are that the .NET applications is performing better on the average. but of course this is not a fair comparison. A VFP/SQL server application probably always outperforms .NET becuase VFP is optimized in handling data. But if this really is significant really depends on you implementation and how the application handles data.

Walter,
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform