Glenn;

Having new and more features can be a dangerous thing. It sure can add to the bug list! Having an engineering background I sometimes like to keep things simple. Like a CD player. The salesman said I “have to have a multi CD changer, for convince”! He went on to state how “impractical single CD players were. I told him I would only buy a single CD player as a multi CD player will fail due to the additional complexity of mechanical and electrical components involved.

Sometimes simple is better but then we would never progress in the software world. At Microsoft the word “progress” is $$$$$$! For the user it is "Wait for the next Service Pack and pray things get better!

Tom



>Hi James,
>
>VFP 7.0 is not without sin! It can cause a similar effect which not only removes source but fills with "garbage". I understand this is a known bug and will be fixed. I do not know under what circumstances this ugly bug decides to attack but as the boy scout code states "Be Prepared"
>
>By the way another anomolous behavior is showing up while I edit class methods, when I hit the space bar after the first operand of an instruction and intellisence kicks in sometimes I get a bonus of several "garbage" characters before my operator. I can not reliably reproduce this problem so I have not reported it. I am curious however if anyyone else has seen this one.
>
>Glenn
>
>>Hi Darek,
>>
>>Lest you think VFP is picking on you, it happened to a lot of people with VFP 6.0. It seems to be fixed in VFP 7.0.
>>
>>Before it was fixed, however, it used to drive me bats, since you cannot predict when it will happens, so you have to be careful all the time.
>>
>>What happens is you open a class and all your carefully crafted method code is blank. Its not really gone, it just did not appear in the IDE.
>>
>>Here's what you do to get it back.
>>
>>Close the class, but DO NOT SAVE IT. If you save it, your method code will be gone for good.
>>
>>Then, at the command window...
>>
>>CLEAR ALL
>>CLOSE ALL
>>RELEASE ALL
>>
>>Then, reopen the class. Your custom code should be back.
>>
>>Regards,