>A general rule I have tried to obey is to take not more than 1.5 seconds for a form to instantiate. More time than 1.5 seconds and a user becomes concerned which is not good.


I'd be thrilled if we could get it down to 5 seconds


>
>A vcx file seems to speed things up over creation using procedural code. However, you have to watch out that your vcx library does not become too “heavy” as that can also give you a hit.

If this is a marginal (10%) difference, it is probably not going to solve our problem.



Another area to consider is how do you populate the forms with data? The quickest way is to open tables first when the application is first brought up. Then the forms do not have to wait for the data to be available.

This is a relatively minor factor per the profile.



>>ers are "more patient" when an application first is brought up. Waiting for a form is a different story.
>

We have the time balanced as best possibe between start-up and form display



>There are a few things you can do to speed up this process.

Oh please, what are they?



The biggest problem is to define a realistic CPU speed as a suggested minimum for your application. Choose a real number that seems practical and use that as your benchmark and make that a system requirement. If someone has a 100 Mhz CPU it may prevent a sale of your product. It may be impossible to satisfy such a customer. It is understood that not all customers run out to buy the fastest equipment when it becomes available (every other day?) but there has to be a realistic balance between computer speed and application requirements.
>


absolutely. We don't need to support 166's. We do need to support 450's.
>
>
>Tom
>


Thank you very much for your thoughts, Tom,

Jack