[AccessD] Form Controls - Class implementation

The form code:

Option Compare Database
Option Explicit

Public fclsCtlSortSupervisor As clsCtlSortSupervisor


Private Sub Form_Open(Cancel As Integer)
     Set fclsCtlSortSupervisor = New clsCtlSortSupervisor
     fclsCtlSortSupervisor.mInit Me
     MsgBox fclsCtlSortSupervisor.pCtlNames()
End Sub

Private Sub Form_Close()
     Set fclsCtlSortSupervisor = Nothing
End Sub


John W. Colby
www.ColbyConsulting.com


A.D.Tejpal wrote:
> Run time handling of form controls in the order of tab index.
> ========================================
> 
>     Use of a collection as suggested by J.C., appears to be the optimum 
> approach, provided the point raised by Ken is addressed suitably. A form 
> having three tab controls each with 4 pages, would need 15 collections as 
> each form section or tab control page has its own set of tab indices for 
> controls located therein.
> 
>     There could be an interesting way to handle this requirement 
> conveniently by adoption of a single collection where each of its elements 
> is itself a collection, permitting a generic subroutine to handle unlimited 
> number of tab control pages apart from the three form sections (detail, 
> header & footer)