I'm not sure we should be singling out Canadians here. If anything, the US situation is the exception, since SQL Server uses a SQL collation by default for the US, for backward-compatibility reasons. The rest of us, by and large, get a Windows collation on a default install.
Thanks for that point, Paul. I hadn't realized this, being the comfortably provincial, geo-focused American that I am
Someone posted a link here for the default collations, but that was for 2008. Here's the list for 2005 (which the QotD was about):http://msdn.microsoft.com/en-us/library/ms143508%28v=SQL.90%29.aspx
And, indeed, most collations listed are Windows -- not SQL -- collations.
Kudos to the o.p. for tracking down a hung Access process to this problem. I'd be curious what your trouble-shooting steps were? Did you see the identical process succeed in U.S. locations and decide there was something about Canada? Me, I would have looked for something specific to that Canadian server and missed the forest for the trees, that the problem was global to the SQL installation/collation.
Thanks for the question. The specific problem will almost certainly never be an issue for me, but the lesson in keeping an open mind during troubleshooting is valuable.