I'll have to think if there's an easier way (sort of tied up at the moment) but I will say that you have an interesting issue about destroying the executable when done. Most likely, you'll try to do this from within the executable, which should be tricky, since it'll be running at the moment. Possibly you can either (1) write a "killer" app :) that you launch so that after Director exits it can kill the file(s) or (2) use the scheduler or something or batch file or registry entry such that you kill the app the next time you boot. But somehow you have to either "schedule" the destruction of the app for after the app exits or have something out there waiting. It depends on how critical the cleanup needs to be. Is it just so that it doesn't sit on the disk forever? Or is it for security?
- Tab
______________________________________________
p e n w o r k s c o r p o r a t i o n
software architecture + multimedia engineering
www.penworks.com
[To remove yourself from this list, or to change to digest mode, go to http://www.penworks.com/lingo-l.cgi To post messages to the list, email [EMAIL PROTECTED] (Problems, email [EMAIL PROTECTED]). Lingo-L is for learning and helping with programming Lingo. Thanks!]
- <lingo-l> Please give me a clue on how to proceed wi... Chris Rasmussen
