>Question about using Modeless forms.
>
>We have 2 very large systems. The one I am working on now currently has 196 forms. The current wisdom seems to be that most if not all forms should be modeless. However, I can find no way to do that in a system this large. As I read the help file and with the programming attempts we have made here, there is no way to start a modeless form once you have run the READ EVENTS. Since I cannot load 200 forms at the start of the program, that seems to leave out any modless forms except for status windows where a process is running such as a reindex. We do have a startup screen that is modless that also serves as the system object holding many system settings.
>
>I was just wondering if I am missing something here or if anyone has any ideas on this. Thanks.

Hi John,

That means that your app model is somewhere short or wrongly establihed to begin with.

Once you correctly establish your app object (module) then
AFAIK There is no limitation in regards of use of modal and modelss froms.

I use old style VFP top menu (mnx) which calls object methods in
each module main prg; something like
oAppObject.ClientsMaintenance()
which is just small proc which intantiates some business object (session object kept in prg usually) and then from there all other forms (modeless/modal) and objects are called. No limits not soever.

If top menu is off your preferences list (they do look ugly nowdays), then you can start module simply by calling some main form to act as top meny with large buttons (I think it should be modal) and then from there you can freely call everything else. There are some cool downloads here on UT
mimicking modern interface patterns which can make that top form look just as good as any other win application.

HTH

Sergio