I have some programs which convert massive amounts (3M RECORD SETS) of data from flat ascii files into various related FP tables. In an attempt to improve performance I liberally used the SP3 command, INDEXSEEK as opposed to SEEk. I found that this function exhibits a nasty memory leak when used in a high volume repetitive loop and have since converted back to SEEK.
Has anyone else experienced a problem with INDEXSEEK?
Suivant
Répondre
Voir le fil de ce thread
Voir le fil de ce thread à partir de ce message seulement
Voir tous les messages de ce thread
Voir tous les messages de ce thread à partir de ce message seulement