Hey RK - I was thinking the same thing. Essentially - Gene - you could do the direct export of data - but, to a CSV file. Then, use lo-level file handling to add the memo field onto each line, and, as RK said - make sure to add in the CRLF.

-K-

On 10/30/2019 7:42 AM, Richard Kaye wrote:

I believe this goes back to dBase compatibility and these commands do the same thing.

It's not too hard to roll your own CSV/Tab delimited file in which case you can keep your memo fields mostly intact. You will need to convert embedded CRLF in order to keep one record per line.

--

rk

-----Original Message----- From: ProfoxTech profoxtech-bounces@leafe.com On Behalf Of Tracy Pearson Sent: Wednesday, October 30, 2019 10:08 AM To: profoxtech@leafe.com Subject: RE: Exporting Tables

Gene,

I have not seen a difference in the output of the two commands.

You might want to consider looking at Craig Boyd's post about exporting and importing from Excel. It doesn't mention Memo fields that I could see. https://www.sweetpotatosoftware.com/blog/index.php/2008/09/30/using-excel-20 07-file-formats-in-vfp-9-0/

HTH, Tracy

-----Original Message----- From: ProfoxTech [mailto:profoxtech-bounces@leafe.com] On Behalf Of Gene Wirchenko Sent: Wednesday, October 30, 2019 9:58 AM To: profoxtech@leafe.com Subject: Exporting Tables

Hello:

   I am having to do a bunch of data export so have had a closer look at the commands.

1) I am wondering if there is a difference between <vfp>
        COPY TO ... TYPE ...

</vfp> and <vfp> EXPORT TO ... TYPE ... </vfp> where the type is XLS or XL5.

2) I know that memo columns are not exported so for tables with them, I am creating a cursor with the memo columns replaced with

C(254) columns. In a few cases, this will result in data being clipped. Short of programming my exports to use Office Automation, is there a way around this? (I mean that is not a kludge. For example, I could create multiple columns each with a piece of the memo, but that would be horribly ugly.)

Sincerely,

Gene Wirchenko

[excessive quoting removed by server]

True. Yeah - LLIO can be more convoluted to code - I'm just more used to doing it that way that the TEXT command, thus why I suggested it. Will surely have to seriously consider the TEXT command more so in the future.

-K-

On 10/30/2019 9:46 AM, Richard Kaye wrote:

You don't need LLIO. TEXT...ENDTEXT will do the trick just fine as well as allow you to pre-process any of the data like swapping out CRLF with spaces.

--

rk

-----Original Message----- From: ProfoxTech profoxtech-bounces@leafe.com On Behalf Of Kurt at VR-FX Sent: Wednesday, October 30, 2019 12:43 PM To: profoxtech@leafe.com Subject: Re: Exporting Tables

Hey RK - I was thinking the same thing. Essentially - Gene - you could do the direct export of data - but, to a CSV file. Then, use lo-level file handling to add the memo field onto each line, and, as RK said - make sure to add in the CRLF.

-K-

On 10/30/2019 7:42 AM, Richard Kaye wrote:

...

I believe this goes back to dBase compatibility and these commands do the same thing.

It's not too hard to roll your own CSV/Tab delimited file in which case you can keep your memo fields mostly intact. You will need to convert embedded CRLF in order to keep one record per line.

--

rk

-----Original Message----- From: ProfoxTech profoxtech-bounces@leafe.com On Behalf Of Tracy Pearson Sent: Wednesday, October 30, 2019 10:08 AM To: profoxtech@leafe.com Subject: RE: Exporting Tables

Gene,

I have not seen a difference in the output of the two commands.

You might want to consider looking at Craig Boyd's post about exporting and importing from Excel. It doesn't mention Memo fields that I could see. https://www.sweetpotatosoftware.com/blog/index.php/2008/09/30/using-ex cel-20 07-file-formats-in-vfp-9-0/

HTH, Tracy

-----Original Message----- From: ProfoxTech [mailto:profoxtech-bounces@leafe.com] On Behalf Of Gene Wirchenko Sent: Wednesday, October 30, 2019 9:58 AM To: profoxtech@leafe.com Subject: Exporting Tables

Hello:

    I am having to do a bunch of data export so have had a closer look at the commands.

 1) I am wondering if there is a difference between <vfp>
         COPY TO ... TYPE ...

</vfp> and <vfp> EXPORT TO ... TYPE ... </vfp> where the type is XLS or XL5.

 2) I know that memo columns are not exported so for tables with

them, I am creating a cursor with the memo columns replaced with C(254) columns. In a few cases, this will result in data being clipped. Short of programming my exports to use Office Automation, is there a way around this? (I mean that is not a kludge. For example, I could create multiple columns each with a piece of the memo, but that would be horribly ugly.)

Sincerely,

Gene Wirchenko

[excessive quoting removed by server]