MSWB not accepting qualified keyword as column name

[Glen McAllister]

On opening a Stored Procedure via "ALTER STORED PROCEDURE..." a column name of "<my table>.long" is being flagged as a syntax error when the "long" is unquoted. This is counter to the supposed behaviour of key/reserved words when qualified by a table name as the parser is then supposed to recognise a key/reserved word as a variable.

This does not happen with the same SP in another user's MSWB installation, so there's obviously something set in mine which is causing this. I have checked the preferences on both versions and there are no differences. Does anyone know what could then be causing this (incorrect!) behaviour?