memo field in FoxPro
Mark
I need to import a table from FoxPro 3.0 to Access 2000. I
got an error message "External table is not in the
expected format" when I tried to import/link the table
from FoxPro. I found out the memo field in FoxPro table
caused this error. I tried to change the field format from
memo to text in FoxPro table,but all the data(memo field)
will be truncated after the change being made. I also
tried to open with Excel then export to Access,but same
thing happend again(all the data in memo field were
truncated).
Anyone has idea to make it work?
Thanks in advance.
Mark
Cindy Winegarden
news:057d01c3170c$d1e26f30$a401...@phx.gbl ...
> I need to import a table from FoxPro 3.0 to Access 2000. I
> got an error message "External table is not in the
> expected format" when I tried to import/link the table
> from FoxPro. I found out the memo field in FoxPro table
> caused this error.
What error or behavior makes you think that the memo field in particular is
responsible?
> I tried to change the field format from
> memo to text in FoxPro table,but all the data(memo field)
> will be truncated after the change being made. I also
> tried to open with Excel then export to Access,but same
> thing happend again(all the data in memo field were
> truncated).
Well of course. In FoxPro a character field can only have 254 characters. I
assume Excel has a similar limit and simply truncates what doesn't fit.
Are you using the latest FoxPro and Visual FoxPro ODBC driver, available
from http://msdn.microsoft.com/vfoxpro/downloads/addons/odbc.asp?
Can you successfully import a table with no memo fields?
--
Cindy Winegarden MCSD, Microsoft Visual FoxPro MVP
cindy.wi...@mvps.org http://cindywinegarden.adsl.duke.edu
http://msdn.microsoft.com/vfoxpro http://foxcentral.net
Joe Fallon
Excel 2000 and later can handle memo fields while interacting with Access
2000 or later.
There were some bugs in 97.
The trick is to ensure the memo field appears in the first 8 rows of data so
Access will guess the data type as memo instead of Text 255.
--
Joe Fallon
Access MVP
"Cindy Winegarden" <cindy.wi...@mvps.org> wrote in message
news:%23Eu77I0...@TK2MSFTNGP10.phx.gbl...
H S
I have the same problem.
I can import any dbf file with ease which doesnt have memo field.
Only where memo field is there gives error. Saying "eXTERNAL DATA NOT
IN EXPECTED FORMAT"
Please help me get the memo field in Access.
Thanks
Chill Out !
Champ
----------------------------
"Mark" <mr...@fmo.rutgers.edu> wrote in message news:<057d01c3170c$d1e26f30$a401...@phx.gbl>...
Cindy Winegarden
news:%237X5hN2...@TK2MSFTNGP10.phx.gbl ...
> Hi Cindy,
> Excel 2000 and later can handle memo fields while interacting with
> Access 2000 or later.
> There were some bugs in 97.
>
> The trick is to ensure the memo field appears in the first 8 rows of
> data so Access will guess the data type as memo instead of Text 255.
A FoxPro table would have a memo field in every row if there was a memo
field in the table. I'm assuming that you mean that Excel evaluates the
first 8 rows to determine the data type and there needs to be a memo value
that is greater than 255 characters within the first 8 rows.
Thanks for the information.
Cindy Winegarden
news:d11113f1.03051...@posting.google.com ...
> I can import any dbf file with ease which doesnt have memo field.
>
> Only where memo field is there gives error. Saying "eXTERNAL DATA NOT
> IN EXPECTED FORMAT"
Well, I can import or link a FoxPro file with a memo field easily enough but
the field is truncated.
What is interesting to me is that I tried creating an Access table with a
memo field and pasting in a lot of text. It was also truncated.
Joe Fallon
I am pretty sure that when Access looks at a Fox table with an associated
.fpt file (memo) that it works fine.
--
Joe Fallon
Access MVP
"Cindy Winegarden" <cindy.wi...@mvps.org> wrote in message
news:ul85p2AG...@TK2MSFTNGP10.phx.gbl...