>I have discovered from versions to versions that as my EXE keeps increasing in size, there is less chance of having a success load on the first try of our WWC servers. At server boot, it'll work ok. However, when doing it manually from the DLL status page, it is getting harder and harder to have a success load of all of our WWC server occurences as the size of our EXE keeps growing.
>
>Our EXE is presently at 1.3 meg. Anyone has something biggest than that?
>
>We are doing the manual process if we have to do a maintenance update. For example, if we are updating a table structure, during that time, WWC will respond that we are in exclusive mode. Then, when I am finished, I have to unload the servers and load them again so they'll run in normal mode again. For that, I am using the DLL status page and using unload and load servers. But, that is getting extremly difficult to have them loaded ok. Sometimes, I have to try it for about 5 times then other times it goes up to 20 times until I have a success load.
>
>I understand that this might be caused by excessive traffic when a user is already firing a request to the server when the WWC server instances are loading. I also understand that is it extremly difficult to find a pattern to have it successfull in one shot in order to minimize the down time.
>
>Any comment?

---

This was an Old Question @ forum.

Pack Database is the solution.
If you open the database, you wonder there are many deleted records.
which was the "old version" of your views, table.. etc.

Anyway, 1.3M exe is seem normal.

In my company, with 11-12 forms and excludes all reports,
already 1.66M exe after I pack the database.

My advance is any time you need to change table/view structure,
pack database asap.