Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
X# vs VFP
Message
De
20/10/2019 04:51:35
 
 
À
19/10/2019 21:38:30
Information générale
Forum:
Visual FoxPro
Catégorie:
Visual FoxPro et .NET
Titre:
Divers
Thread ID:
01671547
Message ID:
01671566
Vues:
142
J'aime (1)
> Hi Johan,
> That's useful information. Access is very slow, of course.
Yes, was merely trying to give an idea of speed. Even in that scenario it was acceptable for the quantity of data that had to be "exported".

> And of course SQL Server can hold a table in memory also. The question relates to what happens
> on the client side with a 2GB cursor retrieved from SQL Server, compared to VFP optimized for the same query.
> This is rarely an issue except in reporting where the data has to be munged before the report engine, whichever, runs.

Hank,

It will be managed by the OS to swap to disk when required. Reports are definitely a concern, however I have not yet seen anything posted on the X# forums regarding "out of memory" issues found yet by anybody working with large datasets.
Johan Nel
George, South Africa
Friend of XSharp (FOX) member
E-mail : johan(dot)nel(at)xsinet(dot)co(dot)za
Web site : https://xsharp.info
X# runtime : https://github.com/X-Sharp/XSharpPublic
Radio talk : https://blog.aksel.com/2019/07/why-xsharp-might-be-tool-foxpro.html
Précédent
Répondre
Fil
Voir

Click here to load this message in the networking platform