Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
CHR(0) appearing in cursors after intensive processing
Message
De
21/03/2003 17:31:27
Beth Wetherbee
Virginia Beach Public Schools
Virginia Beach, Virginie, États-Unis
 
 
À
21/03/2003 09:52:55
Information générale
Forum:
Visual FoxPro
Catégorie:
Base de données, Tables, Vues, Index et syntaxe SQL
Divers
Thread ID:
00767980
Message ID:
00768819
Vues:
15
>I think this may be the issue described in KB article http://support.microsoft.com/?id=258734.
>

Sorry about posting this twice - I wanted to make sure you saw this Jim.

In a KB article 136694 about memory management in VFP, it says that 'it is critical that the [page pool] memory be physical, not virtual'. The 258734 article says to set SYS(3050) to SYS(1001). If SYS(1001) returns the amount of virtual memory available, it seems that setting SYS(3050) (the page pool) to SYS(1001) (the amount of virtual memory) would be counter to the advice in KB136694. Am I missing something?

Also, I saw another message from you (ID 558694) about SYS(3050), where you said that setting the buffer size to the 256KB minimum would force 'any data which exceeds the buffer size to be written to disk in either tables or temp files'. So, I thought that doing SYS(3050, 1, 262144) and SYS(3050, 2, 262144) in the bigcur.prg would force the cursor to be written to disk immediately, and thus make the CHR(0) problem go away. But, it didn't. Can you help me understand why that didn't work?

I'm really nervous about changing the SYS(3050) setting in my app.

Thanks for your patience,
Beth Wetherbee, MCSD
VBCPS
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform