7 |
The LA Fox DeveloDer Newsletter
|
Janudry
1996
|
(Ed. Note: This thread was sent to us by Bob Timney, newsletter editor from the Potomac Area Fox Users Group.]
ELIN LANDENBURGER, 74503,57
Barry R. Lee, 72723,3422
Tom Meeks, 70304,2176
Bob Petty, 72163,2472
Olin Robie, 74462,1554
RICHARD L WAINWRIGHT, 75521,2530 DATE:
1/5/9612:12 PM
Craig Berntson <CRAlG@teltrust.com> wrote:
3.Ob primarily addresses Win32s problems, but fixes several other minor things. (The beta documentation I saw clearly stated this.) As I have stated in other messages, it does not fix the memory leak problem in Win95, which, according to some people is not a problem with VFP, but rather a problem with Win95.
<SNIP>
Hi Craig. Sounds likes someone at Microsoft is not telling someone else what is or is not going on. I hear what you say about the GDI leak not being fixed for 3.Ob and I can’t match your insider info however I have just given the Microsoft Knowledge base a bit of a stir and there are 220 articles listed against a search on buglist3.00 (the number has gone up by about 25 over the last few weeks!). Of these 56 are listed as having been fixed
in
release 3.Ob (much better than has been rumoured but still a long way to go). However the GDI leak is reported as *fixed* for release 3.Ob.
Specifically look up:
FIX: GDI Resource Leak in Visual FoxPro DE in Windows 95 (ARTICLE ID: Q140322)
FIX: Windows 95 GDI Leak with Show Window Contents Setting (ARTICLE ID: Q136338)
FIX: Memory Leak When Scroll Database Designer in Windows 95 (ARTICLE ID: Q138233)
The articles on the leak are clear in their statement of the fault and state that “This problem was corrected in Visual Foxpro 3.Ob for Windows”.
|
For your information the following list is the other 53 3.Ob fixes:
Open
Error
Date
Gnd
Sheet
Dialog
14 Characters
PageFrame
Column
Erratic Behavior
Visual FoxPro
Builder
Structure
Windows 95
FoxPro
Same Data
Clicked
Meg of RAM
Error
Small
Error
Next Get
|
Page 7
|
7 |