New topic: Window.Open does not work until after a MsgBox call
<http://forums.realsoftware.com/viewtopic.php?t=37714> Page 1 of 1 [ 1 post ] Previous topic | Next topic Author Message GregShu Post subject: Window.Open does not work until after a MsgBox callPosted: Fri Feb 18, 2011 3:33 pm Joined: Thu Feb 17, 2011 8:20 pm Posts: 2 My app must be run from a logon script enforced by an AD GPO. As a result it runs after the user logs in but before the OS launches the Windows Explorer app. My app does not initially open a window. It crashes when it reaches the Window.Open statement. My app does not crash under any of the following circumstances: In the same GPO call a VBScript first that opens a dialog using MsgBox. The VBScript that is opening my RB app first opens a dialog using MsgBox. My RB app first opens a dialog using RB's MsgBox call before the Window.Open call. It appears that something has to be done to kick start the windowing system, and calls by VB or RB do this when their respective MsgBox functions are used, but the call to Window.Open is not doing the same initialization. Am I missing an important step? Is this something I can fix? Greg Schumacher Computer Guy Top Display posts from previous: All posts1 day7 days2 weeks1 month3 months6 months1 year Sort by AuthorPost timeSubject AscendingDescending Page 1 of 1 [ 1 post ] -- Over 1500 classes with 29000 functions in one REALbasic plug-in collection. The Monkeybread Software Realbasic Plugin v9.3. http://www.monkeybreadsoftware.de/realbasic/plugins.shtml [email protected]
