I think I've just discovered that VFP 8 has real trouble when dealing with "old" menus, to the point of C0000005'ing. After I went through and opened all the old menus, allowing VFP to "Convert to new menu format," things were ok. Likely a causal relationship. Anybody else notice this?

Eric

RE: Old menus by Leemi

Leemi
Thu Jul 31 11:02:53 CDT 2003

Hi Eric:

While I never rule anything out, I have not heard of many people report
this behavior.

I know we changed the menu format between VFP version 6.0 and 7.0. See
this article for more information:

320266 HOWTO: Convert a Visual FoxPro 7.0 Menu to a Visual FoxPro 6.0 Format
http://support.microsoft.com/?id=320266

What version of Visual FoxPro did you use to create the menus? When you
were getting the C0000005 errors, did you try renaming or deleting the
Foxuser.dbf and Foxuser.fpt files?

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 retires June 30th, 2003
- VFP6 Mainstream Support retires Sept. 30th, 2003

>I think I've just discovered that VFP 8 has real trouble when dealing with
"old" menus, to the >point of C0000005'ing. After I went through and
opened all the old menus, allowing VFP to >"Convert to new menu format,"
things were ok. Likely a causal relationship. Anybody else >notice this?

>Eric


RE: Old menus by Eric

Eric
Thu Aug 07 11:52:10 CDT 2003

After considerably more testing, I may be onto something...

The PageFrame that contained the method which the menu was calling was a little odd in that the first two pages were not called Page1 and Page2 as is their wont, but rather some custom names (pgOpen and pgClose to be exact.) After noticing some other odd behavior in VFP8, I did an ADD CLASS OVERWRITE from an old copy, but no matter what I tried I couldn't get those first two tabs named the way that I wanted them. So I shrugged, changed any references in my code from pgOpen to Page1, and from pgClose to Page2, recompiled, and voila, everything now works fine.

Also, and this was the tipoff that VFP8 really really wants those first two pages to be called Page1 and Page2, the code for those pages didn't come over when I did the ADD CLASS, even though it did come over for all subsequent pages.