Pardon me, David but...

"...how much code you are stuffing in them...". Why would this matter one iota? I mean, I can understand that locking 10 versus 10,000 records (i.e. "how much..." can matter for certain things, but for code itself I'm at a loss. And why would the code's existence in ACCESS/ASSIGN methods be any different than anywhere else?
Similarly, "...be concerned about side effects your code might have..." begs similar questions. ANY code can have 'side-effects' (e.g. CREATE TABLE leaves the table selected, SELECT SQL... INTO CURSOR leaves the cursor as the selected alias, etc. IF there happen to be "side-effects" to the usage of ACCESS/ASSIGN then they ought to be mentioned in documentation and any observations that do not conform to the docs ought to be categorized as a bug (doc or function) and NOT consigned to the 'be concerned about side-effects...' category.

JimN

>Gerry,
>
>Playing the devils advocate here... your unit testing didn't uncover the issue before now?
>
>This whole thread just goes to point out that one has to be careful when access/assign are used, how much code you are stuffing in them, and be concerned about side effects your code might have.
>
>>I'm gratefull that you pointed this out before I released my software and made to look the idiot.