6 Common Compatibility Errors in Web Application Built with MS Access

When you are building a web application with MS Access, it is prudent to give value to compatibly checker errors.

When using MS Access for applications, there is a possibility of coming across a host of errors, once you make use of the Compatibility Checker tool. There are multiple types of errors that can be detected by making use of these feature, and the best part about it is; it not only brings out those errors, but also provides you with a solution to deal with all those errors, and try avoiding them as much as possible. After you run the Compatibility Checker, all the detected errors will be stored separately in a table called the ‘Web Compatibility Issues ’. However, before you can run the web compatibility checker on your web databases, you need to close all your database objects. The scan will begin after all the objects have been shut. A few of such errors are listed below.6 Common Compatibility Errors In Web Application Built With MS Access

  1. ACCWeb102000 – This is the error that will pop up if there is an incompatibility in any of the web objects. This means that the erroneous web object is depending on a web object which isn’t actually a web object at all. For example, a web form displaying information from client query. One of the simplest way to deal with this error is to simply remove the reference to client object.
  2. Bugged By Compatibility Checker ErrorsACCWeb102001 – This error will pop up when there are compatibility issues with the characters used in the object name. This error means the object name consist of a character which is not supported by the web, or is invalid according to its instructions. It is important to always adhere to the guidelines while naming objects.
  3. ACCWeb102004 – This error will pop up when there is incompatibility between the property value and the web database. If the property value is not the default value, it will not be accepted, as only the default value of all indicated properties is accepted by web databases. To avoid this error change the current value of property and add the default value.
  4.  ACCWeb102013 – If you leave the property column blank, then also you will have compatibility issues. If no value has been added against the indicated property, this error will pop up. To avoid it from popping up, add the default value next to the indicated property.
  5.  ACCWeb102015 – This error will pop up if you add a string value that is longer than the acceptable limit. You cannot add a value string that is longer than the integer itself. To deal with this error, shorten the value you have added.
  6. ACCWeb102017 – This error is indicative of the fact that the compatibility check has been canceled. This can happen if you canceled the test, if all objects of databases are not closed, or if the databases is a read only database. Check for either of the mentioned reasons or use a professional Access accdb repair or mdb repair tool to fix the error.

While using MS Access and running compatibility checker error, there are several other errors that you can come across, these are the most common and basic ones. Almost all the errors you face can be avoided by following the simple instructions that have been stated at the start of this article.

Author Introduction:

Vivian Stevens is a data recovery expert in DataNumen, Inc., which is the world leader in data recovery technologies, including SQL Server recovery and excel recovery software products. For more information visit www.datanumen.com

Comments are closed.