> >>Hi Mark, >> >>I'm not as good with VFP as most (99.9%) of the members of the UT but I >would use a different resource file for the Executable, thats how I got my >EXE to run without the toolbars that I have in the Development Envir. >> >>Hope this helps, >> >>>Trying to create production version of a project and when run, whatever >toolbars were active within VFP at the time of the Executable's creation, >are present/visible within the run-time module. >>> >>>What a pain it is to have to close all the active toolbars in VFP before >creating the EXE file. Is there a way to programmatically close all the >system's toolbars so that only mine show up withOUT closing them through >the menu prior to compilation? Relp! >>> >>>TIA! >>> >>> >>> >>>mark@remarkable-systems.com > >Hi, Jon >I don't remember all the details, but the crux of the matter is that >toolbars are windows which may be HIDE'n, SHOW'n, RELEASE'd, ACTIVATE'd and >DEACTIVATE'd. As an example type "DEACTIVATE WINDOW 'Standard'" in the >command window. The toolbar with the file open/close icons etc. will >disappear. Each toolbar has a window name. The CodeBook3 framework runs a >loop DEACTIVATE'ing all toolbars in a hard-coded array. It reactivates all >toolbars that it deactivated on shutdown. > >Hope this helps. >Ned Hi Jon, try to look at Tasm. Traders example. There is routine that works pretty well for this case. It hides all the toolbars, and when releasing it can show them all, if you want. I like this approach, it lets me run the app and return just where I was before. hth Dezider --