Hi Stephen,

While explaining to you my idea I was thinking about several applications, I (or my colleagues) were written. For instance, one of them, there this idea of delay object instantiating, would be a great help, but haven't realized due to overcomplexity of this application, is the user criteria screen. It has 8 pages. Some of them even non-accessable depending on some conditions and saved configuration. However, I have to load them all and instantiate each object on each page. This really takes time. This form takes ~30-45 sec. to appear. Originally the same form was used in run-mode too. Recently my colleague and I made some changes in it, so it only loads in "Design" mode.

I have couple of other applications, where I implemented this idea. I know for sure, that for several applications, like DataDict, for example, user not often goes to the second page (IndxDict). He/she may work with the first page only.

Anyway, this idea may be good for some curcumstances (like mine), but bad for others, so I'm not arguing your approach, I'm just trying to show you, that my idea may have sense for some scenarios.

>Hold up a second
>
>how can you say ;
>
>"Besides, there are lots of situations, when user would never go to second and other pages at all."
>
>Do you do narcotics???
>you have no idea what the form even entails, and in my form the pageframe is the most date-centric part of my form with the most activity
>
>I mean really how can you just say "Never go to the second pageframe" you don't even know how many pages are in the pageframe, I mean really speak when spoken to if your are going to pull facts from outer space, if you have something constructive to say then please chime in but if your going to draw facts from "never-never land" then talk to your imaginary friend
>
>
>
>>Stephen,
>>
>>I didn't notice any delay with my approach. However, the form loading time is decreased, that's important. Besides, there are lots of situations, when user would never go to second and other pages at all. Why we still need to load their objects, if they would not be visible anyway? And I believe I picked this idea from UT some time ago (from Brett Hobbs, if I remember correctly).
>>
>>>>>>If the user would not go to the second and other pages, we save time of form loading...
>>>
>>>thats your advantage to doing it on the fly? I would re-think it
>>>
>>>cause if anybody goes to the pageframe then it would take longer (going by your description)
>>>
>>>I know on my system it looks like once a form is loaded with the pageframe then every page is loaded, cause I have no stall between pages loading, now I know a class loads faster then a form so only a fool would dispute that point
>>>
>>>Yea but we all ready determined that he only needed this form in his program once and he seemed pretty satisfied that I hooked him up
>>>
>>>
>>>
>>>
>>>
>>>
>>>>>No ahead of time I determine all needs and create a pageframe with a page for each possible condition, if I would do it on the fly the app size would be smaller but then it would take longer to load the pageframe
>>>>>
>>>>>Where you gathered that I do it on the fly is beyond me
>>>>>
>>>>>and whats your advantage to doing it on the fly?????
>>>>
>>>>If the user would not go to the second and other pages, we save time of form loading...
>>>>
>>>>I also have situations, where the same form used for different tables (and therefore table structure). In this case I have two different grids, which I instantiate on the fly depending on condition. This works just fine.
>>>>>
>>>>>
>>>>>>Stephen,
>>>>>>
>>>>>>I'm not 100% sure, I understood. You create a page object on the fly, right?
>>>>>>
>>>>>>For instance, I have a form with two pages. I put nothing on the second page. In page Activate I have:
>>>>>>

>>>>>>********************************************************************
>>>>>>*  Description.......: Page2.Activate
>>>>>>*  Calling Samples...: 
>>>>>>*  Parameter List....: 
>>>>>>*  Created by........:  
>>>>>>*  Modified by.......: Nadya Nosonovsky 07/19/2001 01:30:38 PM
>>>>>>********************************************************************
>>>>>>with this
>>>>>>     if type("this.ContPageBrowse")"O"
>>>>>>          .newobject("ContPageBrowse","PageBrowse","phones.vcx")
>>>>>>          .ContPageBrowse.top=1
>>>>>>          .ContPageBrowse.left=1
>>>>>>          .ContPageBrowse.height=.parent.height-25
>>>>>>          .ContPageBrowse.width=.parent.width-3
>>>>>>          .ContPageBrowse.visible=.t.
>>>>>>     endif
>>>>>>     .refresh()
>>>>>>     .ContPageBrowse.grdBldMstr.setfocus()
>>>>>>endwith

>>>>>>
>>>>>>Is it essentially your suggestion or I misunderstood?
>>>>>>
>>>>>>
>>>>>>
>>>>>>>No prob
>>>>>>>
>>>>>>>I have a like issue on a form and I used a pageframe without tabs and it works very speedy and cleanly
>>>>>>>
>>>>>>>>Ok! I wasn't aware that you could have a pageframe without tabs. This will do exactly what I want as I originally had it on a pageframe, but the tabs weren't relevant, disabled or not, under certain conditions. Thanks!
>>>>>>>>
>>>>>>>>>add a pageframe to the form, set "tabs" property to .F., and in the refresh of the form evaluate the condition and show the desired page thisform.pageframe.activepage = nPageNumber