[AccessD] Add-In Express 2009 for Office and .NET (was AccessD Digest, Vol 84, Issue 16)

>
> Max:
> Hmm, still thinking though, why have this restriction anyway, regardless of
> how the count is arrived at.
> I mean, what is the purpose of it?  Does it have some  sort of roll-back
> which I don't  know about?
>

I've never seen or heard of any kind of roll-back.

This is all tied into the automatic control naming. When you insert a
control, it gets named "text123" or whatever. Access maintains a control
counter, so your controls get sequential, unique names. The ItemSuffix
attribute in the SaveAsText file contains this counter.

My speculation is this: the 754 control limit was a strict limit in the
early versions of Access. So, the counter logic was designed to stop at 754.
This legacy has carried on, at least until A2003.

The problem with resetting the counter is controls with default names. If
you have a lbl100, text123, and cbo256, the counter mechanism is going to
barf when you try to add a new control of that type, and the counter happens
to increment to 100, 123 or 256.

If you follow strict discipline, and give ALL of your controls meaningful
names, this won't bite you. But who really does that all the time?

Thus, no code was ever built to reset this counter. Just a lot of work for
no big gain.

-Ken