>I would have liked to have broken it down but the boss want's it all rolled into one exe.

Does he mean Hot Rolled Picked and Oiled?

This may seem like a Old man's yarn, but in the late 70's I developed a system for a steel processor headquartered in Chicago. the system was developed and run on a 64K 20MB system which supported multiple users and was online via a 2400 baud to remote sites in Michigan. Oh did I forget to mention, the system was written in assembler!

>
>All of those forms are not just data entry screens. Some are selection screens for many different types of reports (901 frx's), some are goto's by many different params, in all it's just huge. I can see how to get rid of about half the reports but no go. Maybe on the next version she will change her mind on those.
>
>If I compile a local copy it takes about 5 mins. On the network at the office it takes about 15.
>
>>Hard to beleive any single user has ever used more than 20 screens - but I could be wrong given my limited experience with 'steel slitting'.
>>
>>You documentation must look like the yellow pages!
>>
>>I often break applications into seperate applications, even though they may share the same data files and some prgs and screens. Perhaps your app can be broken down for specific user groups. Fewer options to navigate might make it easier on the users as well.