Problems with FoxPro Drivers

[Marcos]

I keep having these problems with Fox Pro Drivers and DTS packages. If anyone
can help, it would be much appreciated.

I am using Visual Fox Pro 6, with Microsoft Data Access 2.5(MDAC). The driver
for VFP = 6.01.8629.01.

The problem occurs when I try to open or edit a DTS in SQL Server, the driver
appears to be corrupt. I get the following message:

Error Source: Microsoft OLE DB Provider for ODBC Drivers

Error Description: Unspecified Error
Microsoft[ODBC Visual Fox Pro Driver} Cannot open file c:\temp\5ui4000c.tmp

And then I can't view, edit or even run any of my DTS packages. If anyone
has any ideas, I would be much appreciative.

Marcos

[Vince Teachout]

On 29 Aug 2002 09:56:00 -0700, "Marcos" <marcos.romero@chase.com> wrote:

>I keep having these problems with Fox Pro Drivers and DTS packages. If anyone
>can help, it would be much appreciated.
>
>I am using Visual Fox Pro 6, with Microsoft Data Access 2.5(MDAC). The driver
>for VFP = 6.01.8629.01.
>
>The problem occurs when I try to open or edit a DTS in SQL Server, the driver
>appears to be corrupt. I get the following message:
>
>Error Source: Microsoft OLE DB Provider for ODBC Drivers
>
>Error Description: Unspecified Error
>Microsoft[ODBC Visual Fox Pro Driver} Cannot open file c:\temp\5ui4000c.tmp
>
>And then I can't view, edit or even run any of my DTS packages. If anyone
>has any ideas, I would be much appreciative.

This is probably completely useless advice, since I don't know much about SQL,
and nothing about MDAC. But based on similar messages with other products in
the past, I'd first check to be sure you had a c:\temp directory, and next to be
sure you had full rights to it. You've probably already done that, so just
mentioning that on the off chance.

Ignore munged e-mail address above.
If necessary to reply via e-mail, please reply to:
caracal A T caracal D O T net

[Garrett Fitzgerald]

Vince Teachout <SendJunkMailTo@hotmail.com> wrote in
news:79l0nu0tuhbu31gl7en30rn3tp3qb5uvqe@4ax.com:
> But based on similar messages with other products in
> the past, I'd first check to be sure you had a c:\temp directory, and
> next to be sure you had full rights to it. You've probably already
> done that, so just mentioning that on the off chance.

And check the attributes, to make sure the System flag isn't set.