>We are using Foxfire as our report writing tool in a commercial app. We have a dilemma, in that the report controls toolbar doesn't always show when the user is editing the report. (Foxfire uses the VFP report editor). From my understanding, one cannot call native VFP toolbars if they are not already active but hidden. It has been suggested to us that we create custom a custom toolbar with the toolbars>new function, and then drag the desiredbutons to the bar. Since user -defined toolbars can be called with show window even if they haven't been shown before, this sounds like a good bet. I can create a custom toolbar in this manner and close it with the x-box. SHOW WINDOW myreportcontrols will show the toolbar again. Cool. But when I close VFP, and return, the toolbar is no longer defined. The record still exists in the foxuser.dbf, but a SHOW or ACTIVATE WINDOW returns an error.
>
>So my question has 2 parts: if this is the way to go about this, how do I get the toolbar definition to live beyond a VFP session, and perhaps more importantly, is there an easier way to dependable show the report controls toolbar with code? Any guidance will be greatly appreciated.

If not have a special purpose completely set resource off. Otherwise in resource file (use sys(2005) again) replace readonly field with .t. for report controls toolbar after setting its desired position.
Cetin