...so this is what I have gleaned from the above information -- kindly reply with any suggestions:
-- Keep the default AOL available untouched as backup.
-- The AOL on the network is modified by removing all customized objects – only default objects remain (along with macros, master GDL scripts, etc.).
-- The OSL on the network will contain the customized objects (among other things). An OSL object will carry an identifier code (_OSL) at the end of its name to reference the source library and as an indication that it has been altered.
For example, I have customized the Listing Parameters of all our doors and windows so that they can be used in conjunction (with IS) with our standard schedules. In every other way, these are still the default AOL objects, but by moving them out of the default library, I avoid duplication and ensure that the correct object is used. By renaming the customized object, I ensure that it will not be inadvertently over-written during future upgrades.
Of course, I’ll keep a copy of the original AOL on my computer just-in-case.
MacBook Pro Apple M2 Max, 96 GB of RAM
AC27 US (5003) on Mac OS Ventura 13.6.2
Started on AC4.0 in 91/92/93; full-time user since AC8.1 in 2004