On an SQL Server 2000 database I've written a stored procedure that updates a record in an old FoxPro DBF file.
This stored procedure works on my test machine and on another SQL server I tested on. However, I get the following error when I try to create the stored procedure on the production system (also SQL Server 2000)
The trouble seems to be with the OpenRowset command on the following line:
I experimented in Query Analyzer by doing another OpenRowset that just fetched records and got the same error.
Any ideas why it doesn't work on this particular server?
In the mean time, I think I will be comparing the SQL Server versions, services packs, and compare what's in the registry for vfpoledb.dll.
This stored procedure works on my test machine and on another SQL server I tested on. However, I get the following error when I try to create the stored procedure on the production system (also SQL Server 2000)
It's rather puzzling as it works on the other two servers, which as far as I know are identical. I am using the same FoxPro driver in all systems (vfpoledb.dll, version 9.0.0.3504).error said:Server: Msg 7399, Level 16, State 1, Procedure proc_AddCustToScheduler, Line 90
OLE DB provider 'MSDASQL' reported an error.
[OLE/DB provider returned message: [Microsoft][ODBC Driver Manager] Driver does not support this function]
OLE DB error trace [OLE/DB Provider 'MSDASQL' IDBInitialize::Initialize returned 0x80004005: ].
The trouble seems to be with the OpenRowset command on the following line:
Code:
Update openrowset('MSDASQL',
'Driver=Microsoft Visual FoxPro Driver;
SourceDB=\\server\TestDATA;
SourceType=DBF',
'select * from Datadict')
SET Express = @NewID
WHERE [Table]='COMPANYS'
I experimented in Query Analyzer by doing another OpenRowset that just fetched records and got the same error.
Any ideas why it doesn't work on this particular server?
In the mean time, I think I will be comparing the SQL Server versions, services packs, and compare what's in the registry for vfpoledb.dll.