When using msadosql it always returns the number of records
affected or records returned by a SELECT statement.
The access database, which is what the defaults tests are using
doesn't return the number of records for a SELECT.
It's a known issue that you have to MoveLast/MoveFirst before
the correct RecordCount value is return for an Access DB.
--
https://gitlab.winehq.org/wine/wine/-/merge_requests/2216
I ran into some scripts with the following code:
```
DMD CL(0, "HIGHSCORES"), "1> " &HighScoreName(0) & " " &FormatScore(HighScore(0)), "", eNone, eScrollLeft, eNone, 2000, False, ""
```
When there is no space after `&` the `H` in the `HighScoreName` variable is making the parser think it's a hex value.
In real vbscript I tried the following:
```
Dim hescore
hescore = "WOW"
WScript.echo "" &hescore & &h02
```
Syntax error
```
Dim h1score
h1score = "WOW"
WScript.echo "" &h1score & &h02
```
Syntax error
```
Dim hiscore
hiscore = "WOW"
WScript.echo "" &hiscore & &h02
```
WOW2
So it looks like it's checking the next character after the `h` to see if it's a valid hex character.
I believe this MR fixes this case and continues to support the test case:
```
Call ok((&h01or&h02)=3,"&h01or&h02 <> 3")
```
Fixes: https://bugs.winehq.org/show_bug.cgi?id=54493
--
https://gitlab.winehq.org/wine/wine/-/merge_requests/2214