Implicit intersection operator: impact on opening csv files

Detlef_Lewin: thanks for the suggestion, however that also turns what was previously a simple route to edit a csv file into a multi-step process (from open file, make changes, save & close file to rename file, open excel, start wizard, go through steps of wizard, make changes, save & close, rename file back).

SergeiBaklan: thanks, now done that; in my opinion it is a bug, will see if that has any effect.

In the interim I've now created a macro in my personal macro workbook to mitigate:-

Private Sub xlApp_WorkbookOpen(ByVal Wb As Workbook)
If Wb.Name Like "*.csv" Then
Cells.Replace What:="=@", Replacement:="'@", LookAt:=xlPart, SearchOrder _
:=xlByRows, MatchCase:=False, SearchFormat:=False, ReplaceFormat:=False _
, FormulaVersion:=xlReplaceFormula2
End If
End Sub

Not an ideal solution (especially if I need others to make amendments to these files) but will probably suffice.

Detlef_Lewinthanks, however I find that if I double-click the file, click File -> Open and browse, or File -> Open and select from recent file list the file just opens (and is interpreted).

Takmilthanks, unfortunately that doesn't seem to allow (easy) saving after making amendments.

Fundamentally, making simple updates to a csv file used to be simple/straightforward using Excel; if this change in functionality is not a bug (and is working as-expected/as-designed) then I'll need to look into an alternative.