I'm having problems transferring the data from some
tables from a legacy Foxpro 2.5 system to a replacement
SQL 2000 DB.

Essentially for some tables when I try to access the data
I get a JET error message saying that 'External table is
not in the expected format'. I think it may be related to
the size of the table in the source DB.

I'm using using a DBIV connection and this works well for
other tables and has worked in the past on the tables
that now fail. The Visual Foxpro ODBC driver hangs DTS
and the Foxpro 2.5 driver is no longer supported.

It's probably not a show-stopper as I have a utility to
write to text files and I'll be able to import from them,
but it is irritating. I was wondering if anybody else had
come accross this problem.

Thanks in advance,

Bob.

Report this post to a moderator

Not sure if you and I hit the same problem, but try this...... It turns out
that DTS is not going to be able to read a stand alone foxpro data file
(zzzzzzzz.dbf ), however, if you use the Foxpro Developer environment, and
install the DBF into a DBX ( explained in help and Books Online) , then DTS
will deal with it just fine.

G'luck


"Bob Knapton" <robert.knapton@tribaldata.co.uk> wrote in message
news:020e01c29c46$bd6a4fa0$89f
82ecf@TK2MSFTNGXA01...
> I'm having problems transferring the data from some
> tables from a legacy Foxpro 2.5 system to a replacement
> SQL 2000 DB.
>
> Essentially for some tables when I try to access the data
> I get a JET error message saying that 'External table is
> not in the expected format'. I think it may be related to
> the size of the table in the source DB.
>
> I'm using using a DBIV connection and this works well for
> other tables and has worked in the past on the tables
> that now fail. The Visual Foxpro ODBC driver hangs DTS
> and the Foxpro 2.5 driver is no longer supported.
>
> It's probably not a show-stopper as I have a utility to
> write to text files and I'll be able to import from them,
> but it is irritating. I was wondering if anybody else had
> come accross this problem.
>
> Thanks in advance,
>
> Bob.

Report this post to a moderator

Bo <jscott56@netzero.net> scribbled in
news:r%TH9.2708$w03.669542@twister.columbus.rr.com,
>> I'm having problems transferring the data from some
>> tables from a legacy Foxpro 2.5 system to a replacement
>> SQL 2000 DB.
>>
>> Essentially for some tables when I try to access the data
>> I get a JET error message saying that 'External table is
>> not in the expected format'. I think it may be related to
>> the size of the table in the source DB.
>>
>> I'm using using a DBIV connection and this works well for
>> other tables and has worked in the past on the tables
>> that now fail. The Visual Foxpro ODBC driver hangs DTS
>> and the Foxpro 2.5 driver is no longer supported.

> Not sure if you and I hit the same problem, but try this...... It
> turns out that DTS is not going to be able to read a stand alone
> foxpro data file (zzzzzzzz.dbf ), however, if you use the Foxpro
> Developer environment, and install the DBF into a DBX ( explained in
> help and Books Online) , then DTS will deal with it just fine.

Bob and Bo,

The latest FoxPro and Visual FoxPro ODBC driver is available from
http://msdn.microsoft.com/vfoxpro/d...ddons/odbc.asp. It's version
6.1.8629.1.

Bo, are you sure you don't mean that Bob should add the DBFs to a Visual
FoxPro "DBC" or Database Container? I didn't see anything about "DBX" or
"DBC" in the BOL, and there's no DBX in the FoxPro world.
--

Cindy Winegarden MCSD, Microsoft Visual FoxPro MVP
cindy.winegarden@mvps.org http://cindywinegarden.adsl.duke.edu
http://msdn.microsoft.com/vfoxpro http://foxcentral.net

Report this post to a moderator