Note: This API is now obsolete.
Provides constants for compatibility with the Visual Basic 6.0 EOFAction property.
Assembly: Microsoft.VisualBasic.Compatibility.Data (in Microsoft.VisualBasic.Compatibility.Data.dll)
|Keeps the last record as the current record.|
|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.|
|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.|
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.
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 2010. 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.
Windows 7, Windows Vista SP1 or later, Windows XP SP3, Windows XP SP2 x64 Edition, Windows Server 2008 (Server Core not supported), Windows Server 2008 R2 (Server Core supported with SP1 or later), Windows Server 2003 SP2
The .NET Framework does not support all versions of every platform. For a list of the supported versions, see .NET Framework System Requirements.