Something to be wary of... If the file path to your document contains spaces, it might confuse the start command.
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dan Shafer Sent: Friday, July 29, 2005 6:58 PM To: Revolution List Subject: Windows Command Code Resolved Just to close the loop on my earlier question.... Chipp and I walked through on the phone the use of the "start" command in the Win shell and for some reason, it worked fine. I think I was enclosing the file name in quotation marks earlier and when I took them out, voila! So the bare-bones version of this is simplicity itself: on mouseUp if the platform is "Win32" then put "start" && the eBookContents of this stack into openCmd else put "open" && the eBookContents of this stack into openCmd end if put shell (openCmd) into shellResult end mouseUp Lots of error-checking and other stuff to add, of course, but this gets me to the next level. I appreciate everyone's help, esp. Jonathan, who went way above and beyond and, of course, Chipp. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Dan Shafer, Revolution Consultant and Author http://www.shafermedia.com Get my book, "Revolution: Software at the Speed of Thought" From http://www.revolutionpros.com, Click "My Stuff" _______________________________________________ use-revolution mailing list [email protected] Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution _______________________________________________ use-revolution mailing list [email protected] Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
