To Harald Staff, for others, please see my first query
dated 13th, now 4 pages back!
Your comments on FormFun and 'real' VB6 forms are most
interesting. I have very recently(ie yesterday) been
given access to VB6 but have never used it before. I did
note however the automatic install of minimize/maximise
buttons on forms and this may offer a quick solution to
my problem though not without some required learning.

I have just finished what to me is a sizable wbook
project in VBA, in all nearly 6000 lines of code. My aim
was always to work within the constraints of a modal
form. After thorough testing I have not had any code
based bugs from the users so far. However, the users now
say they can get incoming queries which may demand
accessibility to other applications. This means either
closing the data input form with loss of data etc or
delaying their responses hence the request for
minimize/maximise functionality and my dilemma. This on
the one hand is to try and comprehend FormFun's code (no
criticism intended) and adapt it to my project or go on a
quick learning curve and create a VB6 addin with all the
necessary window state precautions etc. The latter means
I would also have to re-think my strategy on menus as for
simplicity I have used six autoshapes each with a macro
attached.

So a VB6 solution is not without a lot of effort but you
suggest a VB6 'real' form is the more robust way. I
accept your experience but why do you feel a FormFun
adaptation is perhaps less robust and do the misgivings
involve minimize/maximize functions?

Thanks for the thought provoking comments so far.

Geoff