Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
List stat
Message
From
21/03/2014 16:33:15
 
 
To
21/03/2014 16:00:04
Mike Yearwood
Toronto, Ontario, Canada
General information
Forum:
Visual FoxPro
Category:
Coding, syntax & commands
Title:
Environment versions
Visual FoxPro:
VFP 9 SP2
OS:
Windows 8
Network:
Windows 2008 Server
Database:
Visual FoxPro
Application:
Desktop
Miscellaneous
Thread ID:
01597032
Message ID:
01597098
Views:
53
>>>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
>>
>>
>>Mike -- what part of "LIST STAT" are you explicitly looking for?
>
>Hi Jim
>
>The entire output of LIST STAT is what seek. Perhaps a more complete snapshot of the entire environment using formats we already know is better? If I want to keep the file, then it might be nice to have a Save As option. Escape should close the instance leaving no junk files around.
>
>Do you already have such a wee beastie?

Mike --

I have never used LIST STAT much, probably because I find all the stuff to be so run together that I just get overwhelmed, and I have my own utility for looking at open tables.

If all you wanted was a utility to dump that same list, I would think that would be a rather straightforward tool to add to Thor (including the "no leaving a file around" part).

For me, if I were to use it, I would want something that did more work -- at least breaking it into separate pages on a pageframe. (I am assuming there are clear indications in the text indicating breaks)
Jim Nelson
Newbury Park, CA
Previous
Reply
Map
View

Click here to load this message in the networking platform