Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Trace window not sizable - Need Guru!
Message
From
09/07/1999 14:05:50
 
 
To
09/07/1999 13:14:41
Cindy Winegarden
Duke University Medical Center
Durham, North Carolina, United States
General information
Forum:
Visual FoxPro
Category:
FoxPro 2.x
Miscellaneous
Thread ID:
00239503
Message ID:
00239545
Views:
22
>Ed,
>
>I did try deleting the relevant records in the FoxUser. (I didn't try deleting the whole FoxUser.) No luck. I will try deleting the whole FoxUser, but that may not work either.
>
>Interesting detail about the non-relevance of the registry. We had a lot of problems running FPW and FPD together at my last job. (Users used the 2 apps back and forth all day.) Gave problems and rebuilding the registry seemed to solve them. People that should have known never mentioned that FPW doesn't interact with the registry.
>

Well, since FPW worked under Win3.x, even prior to the Win32s implementation of registry services for Win3.1x, that ought to tell you something...

>>>One day my FPW 2.6 trace window decided to freeze at a vertical size which allows me to see about 1.5 lines. (Horizontal still sizes normally.)
>>>
>>>Not good for debugging!
>>>
>>>Is this in the Registry somewhere? What is the key?
>>
>>Nope, it's an entry in FOXUSER.DBF - the resource file. Try cleaning it out to get rid of the setting.
>>
>>FWIW, FPW2.6 is a Win16 app - it has no clue about the registry.
>>
>>>
>>>Thanks!
EMail: EdR@edrauh.com
"See, the sun is going down..."
"No, the horizon is moving up!"
- Firesign Theater


NT and Win2K FAQ .. cWashington WSH/ADSI/WMI site
MS WSH site ........... WSH FAQ Site
Wrox Press .............. Win32 Scripting Journal
eSolutions Services, LLC

The Surgeon General has determined that prolonged exposure to the Windows Script Host may be addictive to laboratory mice and codemonkeys
Previous
Reply
Map
View

Click here to load this message in the networking platform