Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
List stat
Message
De
21/03/2014 13:20:20
 
 
À
21/03/2014 12:51:40
Mike Yearwood
Toronto, Ontario, Canada
Information générale
Forum:
Visual FoxPro
Catégorie:
Codage, syntaxe et commandes
Titre:
Versions des environnements
Visual FoxPro:
VFP 9 SP2
OS:
Windows 8
Network:
Windows 2008 Server
Database:
Visual FoxPro
Application:
Desktop
Divers
Thread ID:
01597032
Message ID:
01597076
Vues:
63
>>>Hi all
>>>
>>>Maybe it's a habit, but if so, I'll want an alternative. I find it easier to read the LIST STAT output, than to use SET to look at the open indexes etc at runtime, while debugging/investigating. I don't want the output to dump on the screen. So I often LIST STAT TO STAT.TXT NOCONSOLE. I can type that so fast it is almost instinct. However, I'm leaving little stat.txt files around, and that bugs me.
>>>
>>>What I'm thinking of is a utility that would make this cleaner. I'm imagining instantiating an object, having it LIST STAT TO uniquefilename.TXT NOCONSOLE, open the uniquefilename.txt in a unique window - and stay instantiated until I close the window. I can see having more than one open at a time - as in - I have some tables open so I LIST STAT and then I close one or more and open different ones, and want to see the stat now, or I want to compare two status listings, one before a process and one after, etc.
>>>
>>>If such a thing is not extant, then let's make it.
>>>
>>>Thanks
>>Hi,
>>not sure if this is a question like 'has anybody such a procedure available' or an invitation 'who would like to make such a procedure?'
>>Regards,
>>Koen
>
>It's both. If anybody has such a procedure, I'll take it. If not, let's make one.

I don't know of one, which doesn't mean it's not out there. But whether you find one or write one, seems like a nice addition for Thor.

Tamar
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform