Here are some of the possible values than need changing:
#9x
#9X
#9XX
#9xxxxxxx
#9XXXXXXXXXXXxetc.
And here is how they all should look like when the action is executed upon them
#9X
All I have know is this code for format value
$regexp(%GENRE%,'9XX','9X')With this code the change is done, but only once; and only on capital letters . So it would have to be executed every time unknown amount of times in order to really do the job and with a second version for lower letters and third version taking into account >Xx< and >xX< possibilities
So how do I merge those tasks into one line and loop them until there are no lower and upper case x's left, that are adjacent specifically to >>#9<<
I am making sure because [as always] I did not precise enough: there can be many other values in that tag field; and they all must be left alone exactly as they are. I only need to treat x's [and later on other variations of numbers and letters, to which I will modify the descibed / received code]
What's in the field is a string. A string is a line of text.
Search google for what these regular expression character classes are for
^
$
Basically, these two char classes anchor the search for the regular expression to either the start ^ or end $ of the string.
Meaning the string needs to begin with what regular expression follows. 15minutes on youtube would get you understanding how the basics work.
One vid of thousands on youtube: https://www.youtube.com/watch?v=DRR9fOXkfRE
One textual tagfield contains only one string of characters.
Why don't you distribute the distinguishable data into different tag fields?
This way each different dataset would be accessible by its own tag-field name.
And repairing the incorrect data would be easier.
So it is impossible to loop on something from the middle, especially when it is unknown where exactly it will be [with it beeing sometimes at the very beginning or at the very end or somewhere in the middle]?
But I did list some examples
Normally I just put [in this case] >>##9X<< via the actions, to avoid mistakes
But sometimes I'm just writing [changing, correcting] with a keyboard. I shouldn't do it [to avoid mistakes] but it is easier and quicker sometimes to write just >>9x<< or >>x<< [as I already have big clearing action that takes care of such incomplete codes and turns them into >>##9X<<]. And so I need to not take notice if by mistake there are two x's or three, because of a stuck key or a slip of a finger
Because that would end me up with something like a worksheet in Excel, filled with dozens of columns, but most of witch for most of the time would be empty; and still there would have to be one very wide column to house codes with words and not just with two digits [numbers and combinations o a digit and a letter]. I would need to constantly turn on and off such columns or scroll the view horizontally or work on something like two widescreen monitors. And the numbers of errors coming such unclear views would be horrendous
Instead of that I have one column / tag field to house all the codes [my genres in form of codes]
wordhere9xXxXwordhere
wordhere9xXxX wordhere
wordhere 9xXxXwordhere
word here9xxXx
[...]
Point taken
But all values are marked with markers ["##"] and other action takes care of putting / checking them
And such cases like those above I surely would not want to be treated automatically, because they can indicate a big mess [and as such have to be evaluated manually; or automatically by simply wiped out, which is what happens now in my system]