Just FYI: I found slow development execution in VFP 7 when debugger was open, but only when Show Line Numbers in Trace was set in debugger Options. Take out line numbers and debugger has nearly no speed affect, even though lineno() was in Watch window. Seems to happen particularly when excuting code from the SET PROC file, which contains around 20,000 lines (was ported from FPW 2.6)

And the debugger frequently makes VFP crash completely.

dennis


>>Hi George
>>
>>I have had this happen occasionally. I am just tired of trying to track down these problems so I just restart my machine and carry on. I also have the class browser crash many times if I try to open a parent class that resides in a different class library from subclass that was part of a form I just tested. I constantly have to remember to issue "Clear ALL" after running a form to insure I do not crash. These needs further checking but I have been to busy solving other problems to solve this one.
>>
>>I also have problems with grids with long ControlSource expressions that cause the init method of labels, shapes etc from firing properly resulting in invisible controls that only reappear after you click on the place where they should be displayed. The problems disappears if the ControlSource expression is less complex or if there are less than about 5 records in the grid. When I replace the grids with Listboxes the problem no longer occurs.
>>
>Simon,
>
>My problems haven't been as acute as your's. The reason? I dunno. If I ever have a problem with the Class Browser, I habitually delete the BROWSER.* files.
>
>
>>P.S.
>>I would not be too jealous because the Adaptec Raid Card will not work with the Dual monitor Matrox G550 urgh! So back to a cheap PCI video card. None of the vendors have a solution and each points a finger at the other. Maybe a future BIOS upgrade will solve this one.
>
>Oh! My heart bleeds purple peanut butter for you.< bg >