Hm, that's unusual. From what I can tell, syscurconfigs refers to a compatibility view used for backwards compatibility with SQL Server 2000 (source: http://msdn.microsoft.com/en-us/library/ms177502.aspx). Seems as though it's dynamically constructed when a query is fired at the view, so Access probably can't handle the fact that it won't exist when you're trying to link to it, though I'm not certain if part of your application will need to reach that view or not.

The import/export wizard in SQL Server could well handle your problem as well, though. There is an issue with it in that you wouldn't have real-time data from your SQL Server database; however, if you only need occasional imports and processing of that data, it would definitely work. You could use the wizard to set up a SSIS job to export data from SQL Server into Access, then schedule that package to run at regular intervals, if that's a workable solution in your environment.