OK - this is a very odd problem and everyone I have tried to get help from up to this point has thrown up their hands and given up. Unfortunately, that is just plainly not an option for me.

I have an Access front end to a SQL back end. I go through a process when the user logs on where I look at their settings and grab the data that is pertinent to them from the SQL database and load it locally into local Access back end tables. Are you with me so far? So then they can edit and add records quickly. Once they have completed their work locally they "upload" their data back to the SQL server. I utilize stored procedures to do this as I have users globally. It has taken me many many months to perfect this architecture. It really works very slick and the stored procedures give me a very quick turn around. I went through extensive UAT process with this as well.

I am now in production with this new version of my software. When certain users choose to upload their data back to the SQL Server they get the dreaded "3146 ODBC Call Failed" error message.

Because of other error trapping and other evidence on the server of what's going on - I can pinpoint the stored procedures that are causing this problem. I have checked their ODBC Connection Strings and everything is fine in there.

This is not happening everywhere! I have plenty of users who are running fine! I can't recreate this problem in my own test environment - so I can't step through code to figure out what exactly this error is doing. When I take the users local data file and put it in my test environment - everything runs fine.

All of the other stored procedures that run to load data - lock and unlock data on the SQL Server, etc.... - are running fine - so this can't really be an ODBC error. I have checked the odbc32.dll file on their machines to be sure they are running a current version, and that is fine. All users are running on Windows XP.

As you can probably tell I am very frustrated. I have users who are using the application just fine. And, of course, the ones who are getting the errors (making the application useless) are key users. I can't recreate the errors in order to fix them. I can't even trap the error! It comes up each time as 3146 ODBC Call Failed. That's so generic and tells me nothing. If it was a data issue - like a primary key constraint, etc.... I would be able to recreate the error with their local data file.

I have now spent 3 SLEEPLESS NIGHTS trying to figure this out. I have used NetMeeting to dial in to the user's computer to watch and make sure they're not making some odd user error. They aren't. I'm going insane. Does anyone out there have any ideas? Any thoughts about pointing me in a different direction?

Thank you in advance for any help or direction you can provide!

PamelaDV