Kevin O'Shea wrote: > I found the issue - a colleague had added code to our form's base class > for the Vista Aero display issue - on the init: > > ACTIVATE WINDOW (THIS.NAME) IN SCREEN NOSHOW > > This code was causing forms with similar names to be pulled up in their > opened sequence. I have removed the code for the time being as it was > code put in place in anticipation of our user base going to Vista. Any > suggestions on fixing this code would be appreciated - we have a couple > of ideas: > 1. Give each form a randomly generated name > 2. have a timer event fired at the end of the init (re)fire the Activate > after the form has initialized (using THISFORM.Activate) > 3. Check if VFP SP2 resolves the Vista Aero issue >
Please let us know about #3 above, as I'm under the impression (from others testimony) that SP2 does NOT resolve the issue. -- Michael J. Babcock, MCP MB Software Solutions, LLC http://mbsoftwaresolutions.com http://fabmate.com "Work smarter, not harder, with MBSS custom software solutions!" _______________________________________________ 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/[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.
