Viewing 6 posts - 1 through 6 (of 6 total)
Hello All,
Thank you very much for the feedback and insights. We tried the SSCrazy solution and so far it seems to have worked. We're very optimistic. 🙂
Appreciatively,
SGR
November 17, 2015 at 4:57 pm
A clarification to my post:
The #10054 'forcibly closed' errors aren't sporadic events, as might occur with occasional WAN flakiness. The #10054 errors typically happen within 5 to 10 minutes of...
November 15, 2015 at 7:43 pm
Hello Wendell,
Thank you for the clarification. I tried using a User DSN but it didn't resolve the problem. Will check to see what kind of security we're using.
Best,
Grace
October 12, 2015 at 3:23 pm
Hello Wendell,
Thanks for the lead. Our user base is very small, so User DSNs may be manageable. At least it's worth a test.
October 4, 2015 at 5:32 pm
Hello Wendell
Thank you for your response.
Here are some answers to your questions and some additional information:
- We're running SQL Server 2008.
- The workstations are all MS Windows 7 Professional.
- The...
October 4, 2015 at 1:40 pm
Hello,
Did anyone ever definitively resolve this issue? We're having the same symptoms (i.e. ODBC call failed/general network error) with an Access 2010 front end linked to an SQL Server back...
September 22, 2015 at 5:55 pm
Viewing 6 posts - 1 through 6 (of 6 total)