Description of the Jet 4.0 Database Engine hotfix package for Windows XP SP2, Windows Server 2003 SP1, Windows Server 2003 SP2, Windows Vista, Windows Vista SP1, and Windows Server 2008: October …
Symptoms
This article describes the Microsoft Jet 4.0 Database Engine issues that are fixed in the Jet 4.0 Database Engine hotfix package that is dated October 23, 2007.
Resolution
Issues that the hotfix package fixesThis hotfix package fixes the following issue: The original release of this hotfix introduced an issue that also affects Windows Vista Service Pack 1 (SP1) and Windows Server 2008. Inserts and updates may fail in C++ Microsoft Jet DAO MFC (CDAO) applications after you install Windows Vista SP1 or Windows Server 2008. You may receive the following error message:
The field is too small to accept the amount of data that you tried to add. Try inserting or pasting less data. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
952337?(http://support.microsoft.com/kb/952337/) Insertions and updates in C++ Microsoft Jet DAO MFC applications may not work on a computer that is running Windows Vista Service Pack 1 or Windows Server 2008
This hotfix package fixes the following issues that were not previously documented in a Microsoft Knowledge Base article:When you use an Access database or a Jet database that contains tables that are linked to an Oracle 10g database server, a query may return unexpected results. This issue can occur when the query includes a complex SQL statement that has one or more nested JOIN statements. This issue can occur if the Oracle server was upgraded from an earlier version and the Access table links or Jet table links have not been refreshed after the upgrade.When you use a Microsoft Jet 4.0 database, you may receive an error message that resembles the following:
ApplicationName has encountered a problem and needs to close. We are sorry for the inconvenience. If you were in the middle of something, the information you were working on might be lost. Please tell Microsoft about this problem. We have created an error report that you can send to help us improve ApplicationName. We will treat this report as confidential and anonymous. To see what data this error report contains, click here. When you view the data that the error report contains, you see the following list that contains information about some common error signatures. This information may vary depending on the version of Microsoft Office Access or on the application that you use as the front end for the Jet 4.0 database engine.
Collapse this tableExpand this table
Application nameApplication versionModule nameModule versionOffsetMsaccess.exe10.0.4302.0 Msjet40.dll4.0.6218.0 00021eb3 Msaccess.exe10.0.2627.1 Msjet40.dll4.0.6218.000021eb3 Msaccess.exe10.0.2627.1 Msjet40.dll4.0.2927.17 00021ac2Msaccess.exe11.0.6566.0 Msjet40.dll4.0.9025.000021f23 Msaccess.exe11.0.6566.0 Msjet40.dll4.0.8618.0000221f3Msaccess.exe11.0.5614.0 Msjet40.dll4.0.8618.0000221f3Msaccess.exe11.0.6355.0 Msjet40.dll4.0.8618.0000221f3Msaccess.exe11.0.6501.0 Msjet40.dll4.0.8618.0000221f3Msaccess.exe10.0.2627.1 Msjet40.dll4.0.8618.0000221f3When you use a Microsoft Jet 4.0 database, you may receive an error message that resembles the following:
ApplicationName has encountered a problem and needs to close. We are sorry for the inconvenience. If you were in the middle of something, the information you were working on might be lost. Please tell Microsoft about this problem. We have created an error report that you can send to help us improve ApplicationName. We will treat this report as confidential and anonymous. To see what data this error report contains, click here. When you view the data that the error report contains, you see the following list that contains information about some common error signatures. This information may vary depending on the version of Microsoft Office Access or on the application that you use as the front end for the Jet 4.0 database engine.
Collapse this tableExpand this table
Application nameApplication versionModule nameModule versionOffsetMsaccess.exe 11.0.5614.0Msjet40.dll4.0.8618.000044d29Msaccess.exe11.0.6566.0 Msjet40.dll4.0.8618.000044d29Msaccess.exe10.0.6501.0Msjet40.dll4.0.8618.000044d29Msaccess.exe11.0.5614.0 Msjet40.dll4.0.8618.000044d29Msaccess.exe11.0.6355.0 Msjet40.dll4.0.8618.000044d29Msaccess.exe10.0.2627.1 Msjet40.dll4.0.8618.000044d29When you use a Microsoft Jet 4.0 database, you may receive an error message that resembles the following:
ApplicationName has encountered a problem and needs to close. We are sorry for the inconvenience. If you were in the middle of something, the information you were working on might be lost. Please tell Microsoft about this problem. We have created an error report that you can send to help us improve ApplicationName. We will treat this report as confidential and anonymous. To see what data this error report contains, click here. When you view the data that the error report contains, you see the following list that contains information about some common error signatures. This information may vary depending on the version of Microsoft Office Access or on the application that you use as the front end for the Jet 4.0 database engine.
Collapse this tableExpand this table
Application NameApplication versionModule nameModule versionOffsetIexplore.exe 6.0.2800.1106 Dao360.dll 3.60.8618.0 00002c5e Iexplore.exe 6.0.2900.2180 Dao360.dll 3.60.8618.0 00002c5e Iexplore.exe 6.0.2800.1106 Dao360.dll 3.60.8618.0 00002c0c Iexplore.exe 6.0.2900.2180 Dao360.dll 3.60.8618.0 00002bc9 Msaccess.exe11.0.6355.0 hungapp0.0.0.000000000Msaccess.exe11.0.6566.0 Dao360.dll 3.60.8618.0 00002c5e When you use a Microsoft Jet 4.0 database, you may receive an error message that resembles the following:
ApplicationName has encountered a problem and needs to close. We are sorry for the inconvenience. If you were in the middle of something, the information you were working on might be lost. Please tell Microsoft about this problem. We have created an error report that you can send to help us improve ApplicationName. We will treat this report as confidential and anonymous. To see what data this error report contains, click here. When you view the data that the error report contains, you see the following list that contains information about some common error signatures. This information may vary depending on the version of Microsoft Office Access or on the application that you use as the front end for the Jet 4.0 database engine.
Collapse this tableExpand this table
Application NameApplication versionModule nameModule versionOffsetMsaccess.exe11.0.6566.0 Msjet40.dll4.0.9635.00002f736Msaccess.exe10.0.4302.0 Msjet40.dll4.0.6218.000041681 Msaccess.exe10.0.2627.1 Msjet40.dll4.0.6218.000041681 Msaccess.exe10.0.4302.0 Msjet40.dll4.0.7328.00004234b Msaccess.exe11.0.6566.0 Msjet40.dll4.0.9025.040eaec65 Msaccess.exe10.0.2627.1 Msjet40.dll4.0.4431.3000416d1 When you use a Microsoft Jet 4.0 database, you may receive an error message that resembles the following:
ApplicationName has encountered a problem and needs to close. We are sorry for the inconvenience. If you were in the middle of something, the information you were working on might be lost. Please tell Microsoft about this problem. We have created an error report that you can send to help us improve ApplicationName. We will treat this report as confidential and anonymous. To see what data this error report contains, click here. When you view the data that the error report contains, you see the following list that contains information about some common error signatures. This information may vary depending on the version of Microsoft Office Access or on the application that you use as the front end for the Jet 4.0 database engine.
Collapse this tableExpand this table
Application NameApplication versionModule nameModule versionOffsetMsaccess.exe11.0.6355.0 Msjet40.dll4.0.8618.0000193b8 Msaccess.exe11.0.6566.0 Msjet40.dll4.0.8618.0000193b8 Msaccess.exe11.0.5614.0 Msjet40.dll4.0.8618.0000193b8 Msaccess.exe11.0.6355.0 Msjet40.dll4.0.8618.0000193b8 Msaccess.exe11.0.6501.0 Msjet40.dll4.0.8618.0000193b8 Msaccess.exe10.0.2627.1Msjet40.dll4.0.8618.0000193b8 Msaccess.exe10.0.6771.0Msjet40.dll4.0.8618.0000221f3 Msaccess.exe10.0.4302.0 Msjet40.dll4.0.8618.0000221f3
Code Issues specific to partial methods
There are several conditions that are applied to partial methods, such as:
Partial methods must be void
Signatures of both parts of partial methods must match
Access modifiers are not allowed for partial methods
Partial methods must be declared in partial classes
etc
You don’t have to remember all these conditions if you have the CodeRush code issues feature turned on. When the rule of the partial method declaration is violated, code issues will show you an error or a hint, and you can fix it before you compile the code. These code issues are:
Partial method cannot have access modifiers or the virtual, abstract, override, new, sealed, or extern modifiers
If a partial method has an invalid modifier (e.g., virtual, abstract, override, new, sealed, extern, or an access modifier) you will see an error in the code editor, because partial methods cannot have these type of modifiers:
CodeRush Partial method cannot have modifiers
CodeRush Partial method cannot have access modifiers
Partial method cannot have out parameters
Out parameters are not allowed for partial methods. If a partial method is declared with ‘out’ parameters, you will see an error:
CodeRush Partial method cannot have out parameters
Partial method must be declared within a partial class or partial struct
Partial methods can only reside inside a partial class or a partial structure, otherwise, an error is shown:
CodeRush Partial method must be declared within a partial class
Partial method has only single part
When the partial method has only a single part without a declaration, it does not need to be declared as partial. This code issue has a hint type:
CodeRush Partial method has only single part
Custom Exceptions in .NET
The .NET Framework provides a rich set of system-defined exception types that can be thrown and caught by the C# developer. However, the list of available exceptions does not cover every eventuality and often it is more appropriate to define custom exceptions for specific error scenarios. This can be achieved by deriving a new exception class from any of the existing types, usually the ApplicationException class.
In the final section of this article we will define a new exception class and demonstrate how it may be thrown and handled. This will be a simple exception with no custom methods or properties. These can be added to the derived class using standard object-oriented programming techniques. However, this is beyond the scope of the C# Fundamentals tutorial and will instead be described in a future object-oriented programming tutorial.
What is Exception.InnerException in .NET
When an exception X is thrown as a direct result of a previous exception Y, the InnerException property of X should contain a reference to Y.
Use the InnerException property to obtain the set of exceptions that led to the current exception.
You can create a new exception that catches an earlier exception. The code that handles the second exception can make use of the additional information from the earlier exception to handle the error more appropriately.
Suppose that there is a function that reads a file and formats the data from that file. In this example, as the code tries to read the file, an IOException is thrown. The function catches the IOException and throws a FileNotFoundException. The IOException could be saved in the InnerException property of the FileNotFoundException, enabling the code that catches the FileNotFoundException to examine what causes the initial error.
The InnerException property, which holds a reference to the inner exception, is set upon initialization of the exception object.
Why Throw Exceptions? (.NET Topic)
During normal processing, it is possible for an error condition to be detected. In older languages the method or subroutine would be exited early and a return code would be used to indicate the error status. When developing software for the .NET framework, this method is possible but does not provide all of the flexibility of exception handling that is provided by C#. It is preferable, therefore, to raise or throw exceptions explicitly when error conditions occurs and allow exceptions to be captured by the next available try / catch / finally block or by the C# runtime system.
It is important that exceptions are thrown only when an unexpected or invalid activity occurs that prevents a method from completing its normal function. Exception handling introduces a small overhead and lowers performance so should not be used for normal program flow instead of conditional processing. It can also be difficult to maintain code that misuses exception handling in this way.
Exceptions Overview in .NET
- Exceptions are types that all ultimately derive from System.Exception.
- Exception objects contain detailed information about the error, such as the state of the call stack and a text description of the error
- Code in a finally block is executed even if an exception is thrown. Use a finally block to release resources, for example to close any streams or files that were opened in the try block.
- Use a try block around the statements that might throw exceptions.
- Once an exception occurs in the try block, the flow of control jumps to the first associated exception handler that is present anywhere in the call stack. In C#, the catch keyword is used to define an exception handler.
- If no exception handler for a given exception is present, the program stops executing with an error message.
- Do not catch an exception unless you can handle it and leave the application in a known state. If you catch System.Exception, rethrow it using the throw keyword at the end of the catch block.
- If a catch block defines an exception variable, you can use it to obtain more information about the type of exception that occurred.
- Exceptions can be explicitly generated by a program by using the throw keyword.
?
What is break mode? What are the options to step through code?
What is break mode? What are the options to step through code?
Break mode lets you to observe code line to line in order to locate error.
VS.NET provides following option to step through code.
Step Into
Step Over
Step Out
Run To Cursor
Set Next Statement
.NET debug and trace classes - August 25, 2008 at 18:00 PM by Amit Satpute
What is Break mode?
When changes are made to the code in an application, the way to be able to view how those changes have changed the way of execution is Break Mode. In break mode, a snapshot of the running application is taken in which the status and values of all the variables is stored.
