[AccessD] Update or CancelUpdate Without Addnew or Edit

 > Wiser heads have always waited to load the subforms until they're needed.

Indeed.

In fact that is precisely what Max is doing as well, he is just placing dozens of buttons on the 
form to simulate the dozens of pages of the tab control.  One tab control with N pages or N buttons.

But in fact both approaches do in fact load the subform "on demand".  Just In Time Subforms.

However... Max could refactor his solution to use a TAB, much more easily than we could refactor 
ours to use his buttons.  And get rid of a ton of event stubs in the CBF in the process.

John W. Colby
www.ColbyConsulting.com


Charlotte Foust wrote:
> No, Max, you aren't listening.  Tabs load only what you tell them to
> load and when.  If you don't tell them to load a subform until a
> specified event, they don't load a subform.  They're very considerate
> that way.  You built your own speed problem by following Microsoft's
> instructions and putting all the subform objects into the subform
> controls at design time.  That isn't an issue with the tab control,
> which is merely a container.  It's an issue of design of the application
> you're building, not the tools available to you.
> 
> Wiser heads have always waited to load the subforms until they're
> needed.  That works just as well with a tab control and saves you a
> bunch of subform swapping because the overhead is for the initial load.
> After that, you can leave the darn thing on its tab without incurring
> additional overhead.  However, you do incur additional overhead if you
> unload and load subforms over and over. 
> 
> Charlotte Foust
> 
> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Max Wanadoo
> Sent: Monday, September 21, 2009 2:12 PM
> To: 'Access Developers discussion and problem solving'
> Subject: Re: [AccessD] Update or CancelUpdate Without Addnew or Edit
> 
>> but why make extra work for yourself
> 
> 1. You have to do the work anyway for a Tab. So, it is just as easy to
> do it in a subform.
> 
> 2. Tabs DO load when the form opens and they run the code on those tabs
> too including populating the combos, listboxes, etc.  Which is why it
> was making one of my forms run so slow on load and subsequent tabbing
> between them.
> 
> 3. I also put a "Blank" Button option (ie, Tab replacement) on the Main
> Form along with there others; which just loads a blank/empty sub form.
> This is extremely useful when scrolling through records where you just
> need to look at the info on the Main Form until you find the records you
> are searching for and then you can click on whichever button you want to
> load that info you are interested in.
> 
> 4. The wheel was reinvented because it was square.  This makes it nice
> and round and it rolls really well, uphill and down.
> 
> At the risk of repeating myself.  My Tab form was unworkable because of
> the speed issue.  Replacing tabs with buttons made it slick, fast and a
> delight to use.  It got a 100% approval rating from the users who could
> see no difference but suddenly they were no longer waiting 30=60 seconds
> for movement between records.
> 
> We clearly have a different mindset on this. I am going with what goes
> for me and I pass it on for what it is worth.  I think Doug Steele
> adopted this recommendation a few weeks back and I think had similar
> results.  Perhaps you could give us some feedback - Doug?
> 
> 
> Max
> 
> 
> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Charlotte
> Foust
> Sent: 21 September 2009 21:57
> To: Access Developers discussion and problem solving
> Subject: Re: [AccessD] Update or CancelUpdate Without Addnew or Edit
> 
> Max, you obviously haven't followed the JIT loading threads we've had
> over the years.  Tabs don't load anything you have instantiated.  When I
> built tab forms in Access, they didn't load anything on a page until
> that page got the focus.  The overhead of loading all tabs is enormous,
> but why make extra work for yourself showing and hiding stuff with
> "buttons" on a single parent form and generally reinventing the wheel?  
> 
> Charlotte Foust
> 
>