vba - How to investigate and resolve an (apparent) Access database corruption? -


I have an MS Access Access 2010 database application that is in front of the partition and the backend, which is oddly I have begun to behave and to solve the problem and I know that all the options have ended, 32-bit Access 2010 running on Windows 8.1 ... I have Access 2010 and Access 2013 both installed, But the problem is also completely on the Windows 8.1 system. ZA Install 2010 Access and no Office 2013 is not present. If the app is run using the Access 2010 runtime, then the problem also exists: I front-end is running on my hard disk, not in the dropbox or similar environment. There is a back-end in the drop-box.

There are some elements of the third party in the app - references are shown - Examples of examples exist on both systems with example 1, 2010 and 2013, Example 2 with System Access with Bus Access 2010

Enter image details here

No software has been updated for the preview since December 2013. I have checked that the use of third party versions that I am using is compatible with Windows 8.1.

Symptom:

The application (an unsolved development version) works perfectly in the beginning, but if closed and re-opened, then A typical operation third party tree plantation Mainly active control) Abuse - Right-click event has been triggered multiple times instead of one time (number of times is unpredictable) Mainly two types of visibility equal settings (different data sets Of the Date with the dynamic of the population). A Treeview treats behaviors, does not do one even if I remove all the code from a right-click event, it is fired twice.

This main form configuration and code has not been changed for more than 1 year, do not have treviv config or code I use compact on not off

Whatever I have tried:

If I restore the previous version of the application, then it works. And it has been opened again, does not work. (I have tried to do it with many previous versions of the database).

I tried to import a copy of a main problem from the old working version of the database - the same problem.

I have tried to remove the bad previewview and have tried a new one (one is doing a copy which is copying the copy) - the same problem.

I have tried to create a new blank database and import all the items I have manually referenced once the old one, the same problem.

I have reviewed all these possibilities - I have a similarity with the question that I (Vg last three months) have been using the unsettled keyword but before showing the problem There was no change in the code, nor the main form nor tree view control used it.

I have emailed support team for tree control but they have nothing to suggest that I have not already tried.

I have repaired the establishment of both the reference 2010 and Office 365, if the references are somewhat messy

I have not installed Office 365 and Access 2010, Re-booted and Access 2010 is restored. All office reference references are 14 and the problem still exists (compiled in accde). As soon as I restore Office 365, reference 14 and 15 are merged. (It is also true for the working version which is two years old).

What I have not tried yet:

To see if this is a Windows issue (this system is only available from the beginning of September Return to the worth of two months to see it in use), so that it will not be very difficult. .

Rolling back the version of the app from December 2012 (from previous production) which does not face corruption and manually re-apply for two years of development changes. This will be a mega undertaking ....

Are there any other options for testing or resolution that I can try?

Edit to edit: What worked last

I created a new empty database, except the old database Mainly everything was imported, which I created to look alike and had the same code as a one ... and the problem has gone away. Not very satisfactory as a resolution but it confirms that corruption was somewhere.

Usually Access database corruption affects the VBA module, decreasing the chances of table data. Therefore it is expected that you should be able to copy the data in an empty database, get the VBA code from the old backup (since the last source code update), and it should work to merge both together!


Comments

Popular posts from this blog

winforms - C# Form - Property Change -

java - Algorithm negotiation fail SSH in Jenkins -

java - Messages from .properties file do not display UTF-8 characters -