Hi tommy,

Did you include or not include your REPORT files ?? If yes, exclude them. Since the number of forms are significant, do you think there is a chance of reducing the average form size by making form classes of which many forms could inherit. You could also examine if you could eliminate some forms by making general forms which behaviour is depended by a passing parameter.

If the reports are excluded, the forms definitely are responsable for the large exe size. In the first place it is wise to get rid of some forms and replace them with a general forms or a form which is directly based on classes.

In addition, you could identify redundant coding or setting properties and eliminate them by using classes.

Dataenvironments do also take up significant amounts of memory in a form. You might want to eliminate the dataenvironments by programaticly create them or by using USE and SET RELATION commands in the load event.

Another interesing posibility I'm looking at is store all forms in one DBF, exclude it from the project and use SQL-SELECT to put one form in a temp DBF and use DO FORM (MyTempFile) to start the form. However some adjustements have to be taken to have custom classes work in such way.

Bottom line: The number of forms seem far to many, while you don't seem to use a lot of classes compare to the whole projectsize. Classes are an effective way to reduce the need of large form sizes and with a little creativity you might eliminate some forms.

Walter,