Crashes and Errors in Access application after upgrading to SQL Server 2012 from SQL Server 2008
Posted on 2014-10-14
I am having a terrible time with a Microsoft Access 2010 system running in 2003 mode. We upgraded to SQL Server 2012 from SQL Server 2008 and have had serious problems. There are two main forms for an order entry system and both are experiencing Write Conflict Errors on a form with some bound controls and some unbound. These forms have a "Save" Command button that saves data on the unbound controls.
The interesting thing is that this application runs perfectly with no errors on my old Windows 7 system with SQL Server 2008.
In addition to the Write errors, Access crashes frequently. As a result, Control Source values set via VBA for various text boxes are being hardwired in the Control Source properties. When this happens, the correct values are not refreshing in these text boxes. I thought my new code were causing refresh problems and started building in a series of "Requery" and "Save" actions, trying to force the refresh, with unsuccessful results.
i have tried numerous ODBC connections using Native Client 10, but I haven't found a permanent solution.
My client has numerous systems running different versions of Windows, Office, etc. One new system they have running Windows 8.1 with Office 365 started crashing when loading the order entry header form for orders. I worked on this problem using "stops" and "break points" in code trying to find the offending line of code. Finally I found a subroutine that initiated the crash. There appeared to be nothing in this code that was incorrect. I swapped a DIM line with an executable line (why, I don't remember), but walaa, no more crashing. Just swapping two lines of code should have done nothing as one was the only line executing.
Well, I received a call the next day telling me the system was crashing again.
Please help, this system has been running for my client for over 15 years. Every time Microsoft upgrades their versions of Office, Operating Systems, and SQL Server, the system becomes less stable.
Would it help to try eliminating the 2003 mode? I made a quick effort to save the database in 2010 mode but it would not save properly.
Thanks for any suggestions!!!!