Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Object to Data
Message
De
16/03/2011 03:57:02
 
 
À
09/03/2011 05:02:48
Information générale
Forum:
Visual FoxPro
Catégorie:
Base de données, Tables, Vues, Index et syntaxe SQL
Titre:
Versions des environnements
Visual FoxPro:
VFP 9 SP2
OS:
Windows 7
Network:
Windows 2003 Server
Database:
Visual FoxPro
Application:
Desktop
Divers
Thread ID:
01502925
Message ID:
01503839
Vues:
58
Thought I would post a results message to the end of this thread.

1. Building a single replace statement and using macro expansion to run DID improve performance

2. Building a single "UPDATE" statement and using macro expansion did NOT, indeed it made things worse.

3. Using GETPEM() DID improve performance, quite considerably actually.

4. Changing memory management DID improve performance, minimal memory when running USE/REPLACE
maximum when running SELECT statement. I actually made it a workstation setting and we run a speed test utility on each
workstation to calculate optimal memory settings.

5. I changed from using aMembers, I created my own array of fields as part of the scatter data method,
scanning through my own array IS faster than aMembers!.

I have not yet gone over to separate cloned objects and using CompObj() but I am looking into it.

Hope above helps anyone else in similar positions.


Gary.
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform