You're absolutely right, View menu has this bug (the same hot key for two options). The thow possible workarounds here:
1) check number of the needed bar (using PRMBAR()) and then instead of KEYBOARD '{l}', send KEYBOARD '{DNARROW}' needed number of time and then '{ENTER}'
2) provide that there is no open tables in current work area, i.e. issue SELECT 0

 is just HTML operator to make UT replies look nicer.


>Edward,
>
>Thanks for the response.  I'm about at the end of my rope.  I thought that VFP was going to give me much more control than 2.6 but I keep running into meaningless barriers like this.
>
>I've been messing with this all day.  The problem is that if I include the View menu in my app then the user is also exposed to the Data Enviornment control and the Tabel Designer control and there is no system menu pad names that I can find to at least dimm them out.
>
>I've messed with the NOWAIT clause trying to call up the Report Control and then getting rid of the View Menu but without success.
>
>The <pre> and

that you used in your example look real familiar. What do they signify? The "RETURN" that you have in your example; are you suggesting a possible routine before the calling of the actual MODIFY REPORT window?
>
>Another problem is that, if a report is saved with the Report Control active, then the Report Control will also pop up when one does a LABEL FORM ... PREVIEW. Why FoxPro thinks it is necessary to have a Report Control tool bar open during a PRINT PREVIEW is beyond me.
>
>If you can think of anything let me know and I'm curious about the

.  I might try the idea of a NOWAIT routine befor a regular MODIFY REPORT.
>
>Thanks again.
>
>Ed
>
>>>Is there any way to call up the Report Controls tool bar programmatically in VFP 5.0?
>>>
>>>Help says that the tool bar will appear automatically when a MODIFY REPORT is issued.  The behavior that I have seen is that the tool bar will come up automatically only if it was there before.  If not, you have to get it via the View / Tools menu.
>>>
>>>The problem is in APPS when the View / Tools menu is not available.  Assumeing I could get it to come up the first time a user wanted to MODIFY a REPORT, if s/he ever turned it off then it would be lost for ever without a programmatic way of turning it back on again.
>>>
>>>New to VFP so help is definitely appreciated.
>>>
>>>Ed
>>
>>You should include View/Tools menu in your app menu. Then run something like:
>><pre>
>>modify report d:\vfp5test\report1 nowait
>>if not wexist("Report Controls")
>> keyboard '{Alt+V}'
>> keyboard '{l}'
>>endif
>>return
>>