[AccessD] Form Controls

Not knowing what the code was it is tough to figure out the help comment. I am guessing that the 
code used a class somehow.

Collections are part of VBA (Access' visual basic language).  Classes are NOT required to use 
collections in Access.

Glad you got it working.  Collections are way cool for this kind of stuff.

John W. Colby
www.ColbyConsulting.com


Tony Septav wrote:
> Hey All
> Pretty cool I must say.
> Used a combination of John's code and HELP.
> Ran into a error message problem, because I am not totally competent in 
> using collections didn't quite understand what was causing it
> Finally figured out I had to insert the HasProperty Function, Jack and 
> Pat provided..
> Now just have to incorporate the ctl.Tag into the code and "I am good to 
> go".
> 
> This may sound like a pretty dumb question, but in the HELP example it 
> stated "This example only works with host applications that support 
> classes." How do you go about determining if this is true?
> 
> Thanks to All.
> 
> 
> jwcolby wrote:
> 
>> Well, the tab order only works for the section that the focus is in anyway, so have three 
>> collections, one for each section.
>>
>> John W. Colby
>> www.ColbyConsulting.com
>>
>>
>> Kenneth Ismert wrote:
>>  
>>
>>> Hey, all:
>>>
>>> Charlotte Foust:
>>>    
>>>
>>>> If you're talking about in design view, the controls follow the
>>>> order in which they were added, not the tab index, which
>>>> can be changed.
>>>>      
>>>>
>>> That is right initially, but the rendering order determines the Controls
>>> collection order. Using the Bring to Front and Send to Back buttons in form
>>> design view changes the control order. This is how Access handles control
>>> overlap without a z-index property: controls later in the collection render
>>> on top of those before. I'm pretty sure of this.
>>>
>>> Tab indexes, on the other hand, get re-used by section and tab page. This
>>> means that if your form has header, footer  and detail sections, as well as
>>> a tab control with three pages, you could have 6 controls with a tab index
>>> of 1: one for each section and tab page.
>>>
>>> This means that any looping through controls by tab index has to be
>>> recursive. You must go by section, then any tab pages in that section.
>>>
>>> Of course, this complicates adding controls to a collection keyed by tab
>>> index. The straightforward way will work only for the simplest case: only a
>>> detail section with no tab pages. Otherwise, you will get duplicate tab
>>> indexes, and your item add won't work the way you expect.
>>>
>>> -Ken
>>>    
>>>
>