Difficult to say without understanding the query you are running.

Timeout messages can be misleading, but maybe you could rule out a query timeout by increasing your query's ODBC timeout property from the default 60 seconds to a larger value.

If it is really being caused by the data in your view then you could attempt to troubleshoot.. I might try creating a smaller set of test records on the SQL Server end - perhaps SELECT TOP xxx records from your view, and see if your Access query runs with that data. It might help you identify particular data which are causing the issue.