Trimble Access - Line #'s & Default Attributes

Is there a way to have Trimble Access associate the last used default attribute values with the corresponding line code/string # (code/line#)? For example, if l am surveying two or more utility locate lines such as ELEC1, ELEC2,... (base code "ELEC"), have it default the "Last Used" attributes that were entered for the code/string#. Currently, if I survey a point on line ELEC1 and enter the attributes, store the point and then measure a point on the ELEC2 lines, the default attributes are from ELEC1. It would be nice if there was a setting that would default to the "Last Used" attributes from the last code/string# (i.e. ELEC2). I have "Use Attributes from Base Code" enabled as well as the default attributes set to "Last Used" and it works great as it uses the last values for each different code (based on base code only).

In short, I am looking to do the following for measured points using the example base code of "ELEC".

Code "ELEC1" - Use last attributes from last measured "ELEC1" coded point.

Code "ELEC2" - Use last attributes from last measured "ELEC2" coded point.

Short of creating separate codes in the Feature Definition Manager, I have not been able to find a way to do this and the string# examples are just that, examples for those purpose of this post. A real world example of what we use for code/string# would be "ELEC13113" or "ELEC12205", etc.

To clarify, for the example above, if I enter "ELEC1" as the code and populate the attributes, then move over and measure another line and code it as "ELEC2", the attributes for "ELEC1" are the prepopulate defaults (if set to "Last Used").

Anyone have any ideas on how to accomplish keeping the attributes separated for the different strings while using the same "Base Code"? I surely can't be the only one facing this dilemma as it has plagued me since the attribute feature was introduced in "Survey Controller". Don't get me wrong, the attributes are very a valuable asset in our data collection methods which is great for recording anything such as size, material, owner, depth, photos, etc. But when lines have different attributes, it ends being faster to survey one line at a time rather than collecting two or more lines while having to change the attributes back-and-forth between them; even though they run parallel and a few feet apart. It also removes potential human errors.

Thank you for taking the time to read this and I look forward to any comments/replies.