ADODC.EOFActionEnum Enum

Definition

Namespace:

Microsoft.VisualBasic.Compatibility.VB6

Assembly:

Microsoft.VisualBasic.Compatibility.Data.dll

Caution

Microsoft.VisualBasic.Compatibility.* classes are obsolete and supported within 32 bit processes only. http://go.microsoft.com/fwlink/?linkid=160862

Provides constants for compatibility with the Visual Basic 6.0 EOFAction property.

public: enum class ADODC::EOFActionEnum

[System.Obsolete("Microsoft.VisualBasic.Compatibility.* classes are obsolete and supported within 32 bit processes only. http://go.microsoft.com/fwlink/?linkid=160862")]
public enum ADODC.EOFActionEnum

[<System.Obsolete("Microsoft.VisualBasic.Compatibility.* classes are obsolete and supported within 32 bit processes only. http://go.microsoft.com/fwlink/?linkid=160862")>]
type ADODC.EOFActionEnum = 

Public Enum ADODC.EOFActionEnum

Inheritance

Object

ValueType

Enum

ADODC.EOFActionEnum

Attributes

ObsoleteAttribute

Fields

Name	Value	Description
adDoMoveLast	0	Keeps the last record as the current record.
adStayEOF	1	Moving past the end of a Recordset triggers the ADODC's Validation event on the last record, followed by a Reposition event on the invalid (EOF) record. At this point, the MoveNext button on the ADODC is disabled.
adDoAddNew	2	Moving past the last record triggers the ADODC's Validation event to occur on the current record, followed by an automatic AddNew, followed by a Reposition event on the new record.

Remarks

In Visual Basic 6.0, the EOFAction property was used to determine what action the ADODC takes when the EOF property is true.

These constants enable code that has been upgraded from Visual Basic 6.0 to continue to run without additional modification.

Note

Functions and objects in the Microsoft.VisualBasic.Compatibility.VB6 namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.