SQL Server Naming - No, No

MS Access: Check Catalog Msg 3853 Problem

Recently, we had a SQL Server 2005 table we couldn't connect to from MS Access. It turned out the problem was due to an index having a '.' in the indexes name. MS Access didn't recognize this index due to its naming convention.

To work around the connection issue, we created a view and were able to connect to the view which was a SELECT * FROM [PO.TABLE].

The vendor for the software package we were working in is now determining what it will take to rename the index. Undoubtedly, the index is hard coded with that name in many places.

Lesson Learned: don't use periods in your sql object naming convention, period.