Unmatched Background Error - can't read "myoptsfields": no such variable

[sm-shaw]

Guidance
Bug reports are for when HammerDB is not behaving as expected.
Bug reports should not be submitted for help in understanding database performance related questions.
General questions on database performance or HammerDB usability should be submitted under Discussions.

Describe the bug
Get the following when saving MySQL Transaction Counter options in the GUI

Unmatched Background Error - can't read "myoptsfields": no such variable
           while executing
       "subst $myoptsfields "
           invoked from within
       ".countopt.b1 invoke "
           invoked from within
       ".countopt.b1 instate !disabled { .countopt.b1 invoke } "
           invoked from within
       ".countopt.b1 instate pressed { .countopt.b1 state !pressed; .countopt.b1 instate !disabled { .countopt.b1 invoke } } "
           (command bound to event)
       Unmatched Background Error - can't unset "myoptsfields": no such variable
           while executing
       "unset myoptsfields"
           invoked from within
       ".countopt.b2 invoke "
           invoked from within
       ".countopt.b2 instate !disabled { .countopt.b2 invoke } "
           invoked from within
       ".countopt.b2 instate pressed { .countopt.b2 state !pressed; .countopt.b2 instate !disabled { .countopt.b2 invoke } } "
           (command bound to event)

To Reproduce
Use the GUI and set MySQL transaction counter options

Expected behavior
Should not error when saving

Additional context
Found bug when updating PR #670 so change has been included in this PR

Workaround
Set desired parameters in the MySQL build or driver options (they set the same variables) and then start transaction counter running and it will use these variables.

[sm-shaw]

Had used a mix of mysqloptsfields and myoptsfields for variable name.
Fixed in #670 through 0b8dc68 by using same name throughout.