Difference between revisions of "Microsoft Access Error Codes"
Jump to navigation
Jump to search
| Line 4: | Line 4: | ||
== Data type mismatch in criteria expression == | == Data type mismatch in criteria expression == | ||
| − | + | You are using a function, where one of the parameters is ''NULL'' or not of the expected type, the function produces ''#Error'' and you are trying to filter against the result of the function. Even if one single function call will result in #Error this error will be raised. | |
== 49 : Bad DLL Calling Convention == | == 49 : Bad DLL Calling Convention == | ||
| − | + | Your database became corrupt. Decompile the database by using the command line switch ''/decompile'', compact and repair your database. | |
== 2001 : You cancelled the previous operation == | == 2001 : You cancelled the previous operation == | ||
| − | + | You called a domain function like ''DLookup'' and specified a field that does not exist in the table. | |
Revision as of 23:46, 11 February 2012
Microsoft Access is no exception to the rule that Microsoft provides the developer with not very helpful error messages.
In the following some of the most entertaining error codes and their true meaning are described.
Data type mismatch in criteria expression
You are using a function, where one of the parameters is NULL or not of the expected type, the function produces #Error and you are trying to filter against the result of the function. Even if one single function call will result in #Error this error will be raised.
49 : Bad DLL Calling Convention
Your database became corrupt. Decompile the database by using the command line switch /decompile, compact and repair your database.
2001 : You cancelled the previous operation
You called a domain function like DLookup and specified a field that does not exist in the table.