Well I'm back on this one. But I think I've reached a dead-end.... The user is still getting it intermittently. I copied the production data to my machine, and of course I can't reproduce the error no matter what I do. I've run the Exe in production, copied the data to my system and run the exe locally, within VFP, and run the source code inside VFP.
I put the project through code references, it did not find anything. The control the error message refers to is the base VFP combobox, not an inherited class. Error 67 is reported in the GotFocus event line 0. There is no GotFocus() code in the object or anywhere 'up the chain'. In the help file error 67 says "An internal consistency check in the Visual FoxPro expression evaluator failed. This might be caused by a damaged Visual FoxPro object code file. Recompile the program that caused the error." I have recompiled the program several times over the last month so that is not it. Everyone runs the same exe on the server; it is not copied locally so it is not a bad copy of the exe file. The intermittent part is interesting, why sometimes but not others? Re-writing this one form would be a major pain but I may have to do it anyway; if the problem was in a base class other forms would be affected and that has not been the case. Did I mention that I'd like to re-write this app? Lol Lou -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Tracy Pearson Sent: Thursday, November 04, 2010 12:56 PM To: [email protected] Subject: RE: VFP9: Data validator error? Lou Syracuse wrote on 2010-11-04: > Well... The programmer who wrote this system only allows one screen > to be visible at a time so there is no way I or the user can get to > another screen. In fact, he shrinks/expands the VFP main window > around each programmatically in the init(). There is no menu, just a > main form with command button. > > I'm thinking it may be something buried somewhere inside the FFC. I > asked the user to get a screen capture of it the next time it happens. > Lou, Wow, that's dedication to an SDI design. Okay, You have VFP 9 available, use Code References and search for the caption from messagebox. This might give you an idea of where the message is coming from. If the caption doesn't help, perhaps just the "data valid" might find the elusive code. Tracy Pearson PowerChurch Software __________ Information from ESET NOD32 Antivirus, version of virus signature database 5607 (20101110) __________ The message was checked by ESET NOD32 Antivirus. http://www.eset.com _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/03fd01cb8100$34512f70$9cf38e...@com ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
