I live in an MS Access world. I need to import data into a FoxPro DBF table.
I got the following feedback from the creator of that table. Before I get
into this, is there anything special I should know? Will an Access memo
field export to a DBase III DBF file and import into the FoxPro DBF memo
field without issue?

------------------------------------------------
The problem is going to be that Foxpro sees the Memo field in that DBF as a
true "memo" field. That is, you can not import or enter data directly into
that field. It has to be imported as a MEMO type in fox pro.
------------------------------------------------

thanks!

RE: import into memo field by anonymous

anonymous
Fri Mar 05 16:06:05 CST 2004

you can export to dbIV, i'm excetute this example and yes, i can. but with vfp8.0, if you see the information do doble click under word "Memo" in the record, when the first word "memo" is un minus ("m"), it's no have a infermation but if the first word is "M", it has
If you have a form and you take the information for see the client, you can use a editbox.

Re: import into memo field by Cindy

Cindy
Sat Mar 06 11:11:12 CST 2004

In news: yS52c.193705$jH.1984474@twister.tampabay.rr.com,
shank <shank@tampabay.rr.com> wrote:
> I live in an MS Access world. I need to import data into a FoxPro DBF
> table. I got the following feedback from the creator of that table.
> Before I get into this, is there anything special I should know? Will
> an Access memo field export to a DBase III DBF file and import into
> the FoxPro DBF memo field without issue?
>
> ------------------------------------------------
> The problem is going to be that Foxpro sees the Memo field in that
> DBF as a true "memo" field. That is, you can not import or enter
> data directly into that field. It has to be imported as a MEMO type
> in fox pro. ------------------------------------------------

Hi Shank,

I'm not sure what the FoxPro guy meant. You didn't fully describe your
export process - you can export on the Access side or you can import on the
FoxPro side through ODBC.

In Access I exported a table with a memo field to a Dbase IV table. Two
records in my table had data in the memo field and the other was empty. When
an Access table is exported to a DBF format there is no "import" process on
the FoxPro side, you can simply open the table the way you do with any other
table. I was able to open the DBF table in Visual FoxPro 8.0 (the current
version) without any problems whatsoever.

--
Cindy Winegarden MCSD, Microsoft Visual FoxPro MVP
cindy.winegarden@mvps.org www.cindywinegarden.com




Re: import into memo field by shank

shank
Sat Mar 06 12:39:21 CST 2004


"Cindy Winegarden" <cindy.winegarden@mvps.org> wrote in message
news:u$Fun45AEHA.2484@TK2MSFTNGP12.phx.gbl...
> In news: yS52c.193705$jH.1984474@twister.tampabay.rr.com,
> shank <shank@tampabay.rr.com> wrote:
> > I live in an MS Access world. I need to import data into a FoxPro DBF
> > table. I got the following feedback from the creator of that table.
> > Before I get into this, is there anything special I should know? Will
> > an Access memo field export to a DBase III DBF file and import into
> > the FoxPro DBF memo field without issue?
> >
> > ------------------------------------------------
> > The problem is going to be that Foxpro sees the Memo field in that
> > DBF as a true "memo" field. That is, you can not import or enter
> > data directly into that field. It has to be imported as a MEMO type
> > in fox pro. ------------------------------------------------
>
> Hi Shank,
>
> I'm not sure what the FoxPro guy meant. You didn't fully describe your
> export process - you can export on the Access side or you can import on
the
> FoxPro side through ODBC.
>
> In Access I exported a table with a memo field to a Dbase IV table. Two
> records in my table had data in the memo field and the other was empty.
When
> an Access table is exported to a DBF format there is no "import" process
on
> the FoxPro side, you can simply open the table the way you do with any
other
> table. I was able to open the DBF table in Visual FoxPro 8.0 (the current
> version) without any problems whatsoever.
>
> --
> Cindy Winegarden MCSD, Microsoft Visual FoxPro MVP
> cindy.winegarden@mvps.org www.cindywinegarden.com
>
>

I didn't know what he meant either. I have to import into a proprietary
software program that is based on FoxPro and DBF. We are going to test on
Monday. I just wanted a "heads up" warning if necessary.
thanks!