EN
Данное содержимое не доступно на вашем языке, используйте версию на английском языке.

Error Handling Parameters

Windows

Last modified: January 09, 2012

Applies to: Windows | Windows Server

This topic contains parameters that are used for error handling.

JET_paramErrorToString
70
This parameter can be used to convert a JET_ERR into a string. This is done using a special call to JetGetSystemParameter where the integer output buffer contains the JET_ERR value to be converted (as an input parameter) and the string output buffer returns the matching error string. The string will look something like this: "JET_errSuccess,Successful Operation". The string is composed of the symbolic name for the string, then a comma, and then a simple text description of the error. The description string may itself contain commas. If the error is not recognized then the string will be "Unknown Error,Unknown Error".

Note  This parameter is read only.

Default Value:

Special

Type:

Special

Valid Range:

Special

Scope:

Global

Set After JetCreateInstance:

No

Set after JetInit:

No

Affects Physical Layout:

No

Affects Reliability:

No

Affects Performance:

No

Affects Resources:

No

Availability:

All

JET_paramExceptionAction
98
This parameter controls what happens when an exception is thrown by the database engine or code that is called by the database engine. When set to JET_ExceptionMsgBox, any exception will be thrown to the Windows unhandled exception filter. This will result in the exception being handled as an application failure. The intent is to prevent application code from erroneously trying to catch and ignore an exception generated by the database engine. This cannot be allowed because database corruption could occur. If the application wishes to properly handle these exceptions then the protection can be disabled by setting this parameter to JET_ExceptionNone.

Default Value:

JET_ExceptionMsgBox

Type:

Integer

Valid Range:

JET_ExceptionMsgBox, JET_ExceptionNone

Scope:

Global

Set After JetCreateInstance:

Windows 2000, Windows XP and Windows Server 2003:    No

Windows Vista:  Yes

Set after JetInit:

Windows 2000, Windows XP and Windows Server 2003:    No

Windows Vista:  Yes

Affects Physical Layout:

No

Affects Reliability:

Yes

Affects Performance:

No

Affects Resources:

No

Availability:

All

Requirements

Client

Requires Windows Vista, Windows XP, or Windows 2000 Professional.

Server

Requires Windows Server 2008, Windows Server 2003, or Windows 2000 Server.

Header

Declared in Esent.h.

See Also

Показ:
© 2014 Microsoft