Leemi
Mon Jan 05 12:20:32 CST 2004
Hi Cathy:
If the problem is related to file corruption as Eric mentions, then you can
also try issuing a COMILE CLASS <filename.vcx> command from the Command
window. Sometimes simply recompiling the class can fix the error and it is
often easier than recreating the class from scratch.
I hope this helps.
This posting is provided "AS IS" with no warranties, and confers no rights.
Sincerely,
Microsoft FoxPro Technical Support
Lee Mitchell
*-- VFP8 HAS ARRIVED!! --*
Read about all the new features of VFP8 here:
http://www.universalthread.com/VisualFoxPro/News/VFP8Release.asp
Purchase VFP8 here:
http://shop.microsoft.com/Referral/Productinfo.asp?siteID=11518
Keep an eye on the product lifecycle for Visual FoxPro here:
http://support.microsoft.com/default.aspx?id=fh;[ln];lifeprodv
- VFP5 Mainstream Support retired June 30th, 2003
- VFP6 Mainstream Support retires Sept. 30th, 2003
>Hello, Cathy!
>You wrote on Fri, 2 Jan 2004 09:48:04 -0800:
> CN> My INIT() method accepts a number of parameters, and in
> CN> order to make it more readable I separated the line into
> CN> multiple lines.
> CN> Apparently Fox doesn't like that? As long as the
>CN> parameters are all on one line, I can get into the
> CN> subclass.
> CN> What a stupid error!
>I just tried to repro this behavior, but I don't get any error. Do you get
>the same error if you create a new class? If not, then I think the original
>problem was with the VCX/VCT files. (VFP7 SP1)
>--
>Eric den Doop
>www.foxite.com - The Home Of The Visual FoxPro Experts - Powered By VFP8