Hey Mr. B,
Yes, InRoads Survey must have a file format that identifies the Attribute Name, Attribute Value. Otherwise it doesn't know where to assign the value. There is no way that I know of to make InRoads Survey 'automatically' know the Attribute Name. The simplest thing to do would be to call the Attribute Name, 1. So the coding could be simplified to something like: 6611,1,1/2in RLS 26404
And with the Extended Description capability that I discussed earlier, the Attribute Name and Attribute Value can be carried from the Fieldbook to the Geometry and then out to any required reporting.
Now, collecting it as a Note is different.
Collecting it as a Note doesn't require any Attribute Name to identify where it goes within the fieldbook entry structure. There is only one place that a Note goes.
The TIW would be set up to identify the text string after the Code (or wherever it is) as a Note.
In the Fieldbook it was placed in the Note area.
The '$(NOTES) syntax can be used to add Notes into the Custom Operations.
And because you'll probably ask me ; )
Yes, Notes can be added to the Geometry data in the Extended Description just like Attributes, and then reported on in the same way.
This might be more along the lines of what you want to do.
And if you have any more questions on this . . . please . . . keep them to yourself