I never worked with an auto-calendar but what I have read on it it has no benefits against an own created master-calendar. The auto-calendar is a feature which is advertised as a simplification but if I look on the resulting derive-statements I wouldn't say that's more logical and readable as a date-loop to create a calendar. Further I have doubts that the performance within the script as well as within the UI could be better as by a "classical" table even in the best case - but easily the users could disimprove it if they don't comprehend what they are doing there.
Beside this the auto-calendar needs to be created multiple times - in each single application. But a master-calendar (suite) could be created ones - maybe with 10 - 50 years of dates and hundreds of fields, like the normal ones in each kind of numeric/string/dual representation as well as all kinds of flags, rolling periods, min/max value, continuous numbers and whatever might be useful. And the target-applications just call the calendar and pick the wanted periods and fields. I use such an approach against hundreds of applications and since many years without touching the calendar. More simple isn't possible.
