Bill,
We’ve been auto-numbering projects since ABT 5.2 – no problems. We also use auto-numbering on risks, issues, change requests, ideas.
We don’t use auto-numbering on Departments or Locations – they are a number of different formats used as we are a collection of companies assembled over the years, with different finance systems in place. Also, the Department and Location browse windows are not editable, so we can’t replace a generically numbered Department ID or Location ID on this windows with our meaningful, internal IDs in a custom attribute. This is actually what we would prefer to do – we would prefer to use auto-numbering for Department and Location ID’s, as these IDs are used throughout the financial tables and cannot be easily updated if/when we establish a corporate wide standard. We’d like to use the generic numbers where they can’t be updated, but then update the browse windows to display our meaningful numbers in a custom, editable attribute.
Makes sense?
At this point, one has, in many tables, a system generated UID and an auto-numbered ID, where neither are editable, and a third ID in a custom, editable ID field. Do we really need 3 IDs?
Dale