[dba-VB] JIT Subforms, was Merge rows (now: seriously OT)

jwcolby jwcolby at colbyconsulting.com
Tue Sep 22 11:14:07 CDT 2009


Max,

It doesn't have to be either / or.

I used to do the unbind when the user clicked off the tab and William objected, saying that his 
users prefer that it stay bound.  All it takes is removing the form name form the form control and 
voila, it is unloaded.  Leave it there and voila, it stays bound.

My personal feeling is that unbinding it makes a lot of sense when there are a ton of tabs, and / or 
the subforms contain a ton of records.  The time to navigate through the parent record is a lot less 
(faster)

OTOH if there aren't many subforms then it often makes sense to leave it bound.

One way or the other, I do exactly this, decide on a form by form basis whether it makes sense to 
unbind as the user leaves the tab.

With your approach leaving the subforms bound is difficult to say the least.

John W. Colby
www.ColbyConsulting.com


Max Wanadoo wrote:
>> Does that clarify it for you?
> 
> 
> It does, so really with the Tabs JIT you are not much better off.
> 
> With my On-Demand approach, only data that is wanted there-and-now is loaded
> each time you navigate between records AND furthermore, I give them the
> option of a blank sub-form which means there is no extraneous data overhead
> when navigating unless the user wants it.
> 
> I think my On-Demand approach is better for lots of reasons, but if your are
> happy with your JIT-Tabs approach then I am happy for you.
> 
> 
> 
> Max




More information about the dba-VB mailing list