On 2/15/2013 12:21 PM, Kelly Dezotell wrote:
Having a weird problem, and I don't see a solution anywhere else. Please forgive me if this has been asked&answered already.The company I work for is migrating computers from Windows XP 32-bit to Windows 7 64-bit. In the process I'm discovering that we have some programs that call other PRGs, and the 2nd PRG contains only a Class definition with DEFINE CLASS. The 1st program does something like: SET PROCEDURE TO MakeClass.prg ADDITIVE loClass = CREATEOBJECT("MyClass") &&'MyClass' is the class defined in MakeClass.prg In XP, this process works just fine. In Win7, any operation using the LoClass variable after these lines returns an error that the loClass object is undefined. I've tried path configurations, and suffixes and prefixes in the CREATEOBJECT command, with no luck. I realize I can rebuild the class from the PRG to a VCX, but it looks like I may have a dozen or more of these, and rebuilding them all would be a pain. Suggestions? - Kelly
Is your MakeClass.prg in your current path? You must try explicitly putting the path on your SET PROCEDURE line to see if that removes any ambiguity that might be causing the issue.
-- Mike Babcock, MCP MB Software Solutions, LLC President, Chief Software Architect http://mbsoftwaresolutions.com http://fabmate.com http://twitter.com/mbabcock16 _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[email protected] ** 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.
