MLH wrote:
[color=blue]
> Hmmm??? In design view, Access is forgiving (at least,
> Access 97 seems to be). If I manually change a control's
> tab index to 5 at a time when another control already has
> an index value of 5, 97 'sees' it & automatically adjusts all
> the other controls' index values for me.[/color]
Same in 2003. I've not encountered it yet in 2003, but I have had
experience with forms in A97 with large numbers of controls where Access
seemed to get confused when I did the above, to adjust the "natural tab
order" of controls on a form. I'm used to seeing, say in the above
example, the current 5 and following numbers all advance 1 on their own,
retaining the current order. However, in some instances, as I've said,
this doesn't quite happen - the previous '5' would take up some
seemingly (I didn't investigate it thoroughly) random already existing
tab number.
As to the original poster, I would suggest instead of altering the tab
order, to try and do what he's doing by either enabling/disabling
controls after the return of the mid() function. Fiddling with tab
order seems fiddly to me.
--
Tim
http://www.ucs.mun.ca/~tmarshal/
^o<
/#) "Burp-beep, burp-beep, burp-beep?" - Quaker Jake
/^^ "Whatcha doin?" - Ditto "TIM-MAY!!" - Me
