Issue occurs when opening a workspace with certain parameter options, views will not have minimize or maximize buttons and the functions will be disabled in the view's top left windows menu.

In my limited testing this is workspace, dataset, and environment independent.

The target on the shortcut that I used to re-create this problem after fielding a call about it looked like this:
M:\Softrak\GVWIN\GVWin.exe /c /usys /psys /dH:\xxxxx /eSAM /w"H:\xxxxx\yyyyyyy.gvs"

The only modification I had to make to get the min/max functions disabled was to remove the /c. I’m not sure about which of the other parameters might matter, but with those ones on the target line the /c makes the difference for the min/max functionality.

Having the control over the edit permission for users through the /c parameter is vital for idiot-proofing shared views, adding /c to any target line where a user is experiencing this issue is not an acceptable work-around in the long term, and it's a reasonable expectation of users to be able to make use of those functions in a workspace with multiple views.

Hi Warren,

Are you sure that you posted the right screen shot? There are no buttons or context menu's displayed and it's not clear what you are trying to show.

Hi, Warren,

I've tried this using 9.1A(130601) and the original release of (130402).

These are my shortcut properties: C:\Softrak\GVWIN\GVWin.exe /c /uSYS /pSYS /dc:\softrak\oewin\samdata /eSAM /w"C:\softrak\gvwin\views\sales tax report.gvs"

I've tried both a workspace using a single view only and another having multiple views.

I've also tried with and without my Addons folder being active.

I'm not experiencing this problem.

Are you recreating this at both the client site and your own?

Oy, Warren, I'm sorry.

Seems I read your post a couple of times and still managed to turn your /c comment around backwards.

Yes, if I 'remove' the /c parameter, seems the program also removes the minimize/maximize buttons.

Will definitely report this to R&D for you. Thanks for making us aware of the problem.

Oh!!

And you mean the "Minimize/Maximize" Form buttons, not the MIN() or MAX() functions or the Minimum / Maximum Column values.

This is intentional, so that you can have a table containing confidential information for use in a Workspace that the user cannot maximize.

Perhaps this should only happen if the View is "Locked"?

Ahh, I can see why that could be really useful, but yes I think it would be best to tie that behavior to another option.

Since it's working the way it was intended, I've moved the topic out of the "Issues" Forum.

We've recorded this as a suggestion.

I've looked through the GV help and manual and cannot find documentation of this function anywhere near the text "/c" "minimize", or "maximize", so could this thread be moved to the tech support forum so it may be retrievable through google?

Hi, Warren,

Yes, seems this was an undocumented feature in GV. Happens occasionally unfortunately. It will be documented for the next release of GV.

How about if we remove the min/max buttons from minimized Views only when a Workspace is loaded without the "/c" parameter?

I think that meets everyone's requirements and doesn't need the behavior to be tied to another attribute.