It is not the newest nor the fastest thing under the sun but it not a dinosaur either; 2 Duo 2.4 ghz, 3 gb ram XP class machine.

But as I continue to add functions to this five tab page with several repeaters, modal dialogs and ajax callbacks, I'm really starting to wonder how I'm ever going to get back to sub-second hits.

Working in the WConnect 5.x environment is SO nice but are the features of ease starting to pile up and becoming a trade off for performance.

How much improvement should I expect to see by going to COM and pre-compling the pages?

Can't really comment on COM since almost all our customer sites run under COM so that's the norm for us.

In the early days of 5.0 I put some pages out that were compiled at runtime. Switching to pre-compiled seemed to help - but we didn't do any rigorous timing tests so I can't give you any specific results.

But you can't get around the fact that there's still some overhead involved in having VFP generate all that HTML. My slowest page is a form for international students that involves a number of lengthy drop down menus (selecting from a list of countries, etc.) - it does seem to take awhile to draw those up, even tho the page is pre-compiled. These are based on wwWebDropDownList controls - wonder if it would make a difference to fetch the data with Ajax and have Javascript populate the menus?

--stein