Parenthesis In Column Names

Will parenthesis in column names cause problems?

[RWSteele]

When upgrading to SQL Server 2K what problems, if any, can I expect from column names that contain parenthesis?

CREATE TABLE [dbo].[Fail-Status] (
[ID] [nvarchar] (20) COLLATE NOT NULL ,
[Row (X)] [nvarchar] (50) COLLATE NULL ,
[Column (Y)] [nvarchar] (50) NULL

And yes, those are spaces in the column names. Between spaces, parenthesis, and about 40 tables with [ID] as a column name, I've pulled a lot of hair out since taking over this project. And just for the record, I did NOT design this database.

Thanks in advance for any input.

[aspdaddy]

That should be fine in SQL2K.

If you have a lot of dependant views and procedures I'd plan in some database refactoring anyway.

[RWSteele]

Actually the only things I need to worry about are the Access forms used on the client. Of course all SQL is hard-coded, tables are queried directly, and columns are referenced by position instead of name. ex:RS.Fields(0)

If the parens and spaces do become an issue, I thought about creating queries in Access which have the same names as original tables. Then I could rename the tables and columns as needed and use aliases to keep things from breaking. But I'll cross that bridge when I come to it.