>Use the profiler to see what is taking the time. It may be your code which you can optimize for performance. Without profiling the code there is no way to know what, if any, improvement you may get because we have no idea what is taking the time.
>
>What code is running when the user goes from one field to the next? What code is in the inits of the controls? What tables are in the DE, views? How many records are in the views if there are any? Is it possible tio use parameterized views that limit the number of records? Would this 7 page form be better presented as different forms with less controls in them?

Jim,

Thanks for the suggestions. Let me investigate a bit.