Hi Fred,

>I use full tables, not views. From some
>of the comments, I am thinking that this may be a source of some of my troubles. Being self taught, I kind of passed over views
>thinking that I could make do without them. Well, I can if it is a single user application, but client server is another story.


I am "self taught" too, and I had a bear of a time, at first, trying to "get" views. I think I attempted it a number of times and always gave up, but now I'm sold on them. I think one thing that helped, is that I'd found the UT, so I could get some fuzzy ideas cleared up.



>However, I think your suggestion is a valuable one and I am going to spend some time tonight exploring this. It seems like an
>excellent idea to speed up performance. . . if I only create the controls on the non-visable pages
>when the page is selected for the first time, it stands to reason that a lot of 'building and intializing' time could be saved up front,
>especially if those other pages are never accessed. I always put the primary information on the first page.

A bit more info: it's been recommended here to get the form working, w/the controls on the pages, as you've done. Then save all the controls on page 2 to a class, 3 to another class, etc. Then in the ACTIVATE of each page, check to see if the controls exist; if they don't add them to the page, do whatever you need to set them up, and off you go...when the form is loaded, then only the first page instantiates, so it is much faster...then just a short delay for the first time each subsequent page is activated for the first time.

Good luck! J