Windows 11 regional separator character generates access query errors

[grosspeter144]

Changing the Windows 11 Regional Separator setting to the pipe character (|) from a comma (,) results in access queries syntax errors.

For flat file exporting purposes, I changed the Windows 11 Regional Settings Separator Character from a comma to a pipe character. As a result and independently, all Access queries that used commas as separators had their query string commas changed to a pipe characters.

For example, a query with the string Iif([Field] = "Value", True, False) was changed to Iif([Field] = "Value"| True| False). The queries still run, but generate syntax errors when attempting to edit.

Changing the Regional setting back to a comma resolved the Access query edit problem.

Has Microsoft commented on this? Have others experienced this issue?

 

[DickyP]

Sounds like a job for an Import/Export spec (old style) which were invented for just this sort of task if you are doing it in code, or simply choosing you separator if you are doing a manual export.