Software updatesThe following problems are resolved in the OLE DB Provider for Visual FoxPro 9.0:
- The SELECT INTO TABLE command fails without an error message. Also, the CREATE TABLE command works fine.BUG #: 50996 (VSWhidbey)
- You do not receive an error message when you try to create a database by using the OLE DB provider.BUG #: 113173 (VSWhidbey)
- You receive an "OLE object may be corrupt" error message when you open a connection to a table and then execute a stored procedure.BUG #: 125757 (VSWhidbey)
- A connection to an exclusively open database (.dbc) fails and then you are connected to the parent folder. The expected behavior is for the connection should fail completely and not connect to a folder instead.BUG #: 125765 (VSWhidbey)
- You receive an incorrect error message in a stored procedure. Instead, you receive a secondary error message.
- The ADO.NET OleDbCommandBuilder.GetUpdateCommand method fails when a parameterized query is used with the OLE DB Provider for Visual FoxPro.
BUG #: 179173 (VSWhidbey)
- The OLE DB Provider for Visual FoxPro does not support the
SET REFRESH command, the SYS(3050) function, or the SYS(1104) function.
BUG #: 188362 (VSWhidbey)
- When you execute the DROP TABLE command through the OLE DB Provider for Visual FoxPro, the command does not drop the table or report an error message.
BUG #: 244382 (VSWhidbey)
- You cannot query SET("ANSI") by using the OLE DB Provider for Visual FoxPro.
BUG #: 246705 (VSWhidbey)
- The stand-alone Web Setup package for the OLE DB Provider for Visual FoxPro has no label for the "custom" setup option.
BUG #: 286349 (VSWhidbey)
- The stand-alone installation package for the OLE DB Provider for Visual FoxPro writes values to the following registry hives:
- A memory leak occurs in the OLE DB Provider for Visual FoxPro when it is used with the ADO.NET DataReader, OleDbDataAdapter, or ActiveX Data Objects (ADO) in high-availability implementations such as Web applications.
BUG #: 286774 (VSWhidbey)
- You receive an "Unspecified error" error message in the OLE DB Provider for Visual FoxPro under certain circumstances when you run the INSERT INTO command.BUG #: 292112 (VSWhidbey)
- The CHR(0) command is treated as a string terminator for CHARACTER data. This causes random data to be sent to MEMO/CHARACTER BINARY fields through the OLE DB Provider for Visual FoxPro.
BUG #: 302569 (VSWhidbey)
- When you use the OPEN method of the ADODB.RecordSet object together with the OLE DB Provider for Visual FoxPro to open a FoxPro table, you receive the following error message:Exception code c0000005. OLE object may be corruptBUG #: 305670 (VSWhidbey)
- The ADODB Connection.OpenSchema method returns a corrupted recordset when the table name of the data source is more than 128 characters long..
BUG #: 305947 (VSWhidbey)
- You receive error messages when you set the properties of an open ADODB.Connection object. The ADODB.Connection object uses the OLE DB Provider for Visual FoxPro.
BUG #: 324595 (VSWhidbey)
- You receive the following error message from a SQL linked server through the OLE DB Provider for Visual FoxPro:ColumnName was reported to have a PRECISION of N at compile time andBUG #: 325066 (VSWhidbey)
N at run time
- The MODE property on the ADODB.Connection object is ignored by the OLE DB Provider for Visual FoxPro when a table is provided as the data source.
BUG #: 311252 (VSWhidbey)
Behavior changes and additionsThe following changes and additions have been made to the OLE DB Provider for Visual FoxPro. For additional information about Visual FoxPro 9.0 language elements, see the Visual FoxPro product documentation at the following Microsoft Developer Network (MSDN) Web site:
- The following Visual FoxPro functions are now available in the OLE DB Provider for Visual FoxPro:
- The Visual FoxPro EXECSCRIPT function is now available in the OLE DB Provider for Visual FoxPro.
- You can now return more than just a scalar value from a Visual FoxPro stored procedure. To enable this behavior, the following new functions have been added to the Visual FoxPro language:
- As with the Visual FoxPro language itself in Visual FoxPro 9.0, the OLE DB Provider for Visual FoxPro also includes Long Type Name Support in certain data-centric functions and commands. For example, the following CREATE TABLE command is now supported in the OLE DB Provider for Visual FoxPro:Notice the long names for the data types.
CREATE TABLE Test (PKID Integer, FNAME VARCHAR, LNAME VARCHAR, HireDate Date, Notes MEMO)
- The Visual FoxPro SET REFRESH command is now supported inside the OLE DB Provider for Visual FoxPro. This support includes the following commands in the Config.fpw file that is read by the OLE DB Provider for Visual FoxPro:
- SET REFRESH
- The following Visual FoxPro functions are now enabled in the OLE DB Provider for Visual FoxPro:
This function sets the foreground or background buffer memory size.
This function purges memory that has been cached by programs and data. The function also clears and refreshes buffers for open tables.
Article ID: 894012 - Last Review: Jan 16, 2008 - Revision: 1