<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Thank You,<br>
I appreciate everyone's response in trying to help me with the
issues I'm having , this is what I've found...<br>
<b><br>
invfile(42)=invy(367) [did NOT work]</b><b><br>
</b><b>invfile(42)=""{invy(367) [DID WORK]</b><b><br>
</b><b>invfile(42)=""{invy(367){"" [DID WORK]<br>
<br>
</b><b>The above was when exporting the MEMO field as WORD/CSV, not
SLK</b><br>
<p><b><font size="+1" color="#3333ff">Now if I could only get this
to export to a SLK file I'd be golden, ugh</font></b><br>
</p>
<p>After a little more messing around I see that
invfile(42)=""{invy(367) does export the memo but only if I export
it as s CSV "export word invfile=c:\!Output\eBay\eBayInvy.csv)".</p>
<p>for testing purposes I've only populated eight records MEMO
fields with data. When I tried using this "export multi
invfile=c:\!Output\eBay\eBayInvy.slk" to export the data as a SLK
file I get errors when opening the file with excel. <br>
</p>
<p>I just realized now that it was reporting the exact number of
errors as records containing that contained MEMO's. <br>
</p>
<p>It seems like I could be stuck with dealing with a miserable CSV
file which I totally despise. You can't simply just open a CSV
file in excel and make edits, at least not if it contains any data
with leading zero's that you want to retain. Now I'm probably
going to need an xls(refresh) file where I setup everything that
could drop leading zero's as "text" columns and open the CSV with
that before editing anything which just SUCKS! <br>
</p>
<p>I know the CSV actually contains the leading zero's but if you
just double click and open them in excel, it's a mess. It would be
nice if there was some sort of module that could be added to excel
for handling things like this but I've never heard of it.</p>
<p>SLK files retain all of the leading zero's, open just like an XLS
file, and I can save it as whatever I want after making any needed
edits. To me having to deal with UPC's and other fields with
leading zeros SLK was just much easier to use.<br>
</p>
<p>Mike<br>
</p>
<p><br>
</p>
<p><br>
</p>
<br>
<div class="moz-cite-prefix">On 8/16/2017 11:10 AM, Faisal Karim
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:783DA7BA260E5A44A485D801C855DC35ABE44460@ObiWanKenobi.Furniture-Pro.local">
<pre wrap="">Have you tried?
invfile(42)=""{invy(367){""
Faisal
-----Original Message-----
From: Filepro-list [<a class="moz-txt-link-freetext" href="mailto:filepro-list-bounces+faisalk=furniture-pro.com@lists.celestial.com">mailto:filepro-list-bounces+faisalk=furniture-pro.com@lists.celestial.com</a>] On Behalf Of Mike Fedkiw via Filepro-list
Sent: Tuesday, August 15, 2017 6:17 PM
To: Bruce Easton; 0 Filepro List
Subject: Re: exporting MEMO along with other data
Since the ""{ didn't make any difference it's looking like I'm headed in the direction you said in your reply but I'm already having issues.
Everywhere I've looked there's just no examples of exporting the MEMO other than the little bit in the help file to help me.
I'm doing a sub routine to export the MEMO field but nothing works, examples below.
=======================================================
expmemo◄ If:
Then: MEMO invy(367) EXPORT "memo"
=======================================================
expmemo◄ If:
Then: MEMO invy(367) EXPORT "memo.txt"
=======================================================
expmemo◄ If:
Then: MEMO invy(367) EXPORT "c:\memo"
=======================================================
expmemo◄ If:
Then: MEMO invy(367) EXPORT "c:\memo.txt"
=======================================================
Some just got the above got stuck on a black screen, some caused memory errors, etc...
Can someone give me an example, any example of exporting a memo field into a file?
I just hoping the readline stuff will be easier to do because I've never had to use that for anything either.
Mike
On 8/15/2017 1:39 PM, Bruce Easton via Filepro-list wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Mike - the 'memo xx export...' command line should export the data
from the memo field to the destination you specify in that command.
It is then up to you to read that resulting memo-exported file so that
you can then output the data as desired in your 'invfile' export file.
In place of "invfile(42)=invy(367)", you may want to have a 'gosub
getmem, where that subroutine would:
1. export the memo field
2. read the exported memo field file from step 1 (for instance, using
readline loop)
3. massage/select_from the data read in step 2 in order to:
4. then assign to invfile(42) what you need there
On 8/15/17 12:48 PM, Mike Fedkiw via Filepro-list wrote:
</pre>
<blockquote type="cite">
<pre wrap="">windows server 2008 r2,filepro 5.0.05dn9
The line below is what I've been using to export the selected fields
information into a file. It's been working pretty good now, at least
until it gets to the field containing the memo which always winds up
to be a blank column.
export multi invfile=c:\!Output\eBay\eBayInvy.slk
In the help I see this...
"MEMO xx EXPORT filename Exports the MEMO field xx to the
specified filename"
From that I have no clue how to get it to do what I'm needing as far
as the memo.
I've got a ton of fields currently being exported into this file
which all work just fine like...
invfile(1)=invy(1)
invfile(2)=invy(14)
invfile(3)=invy(68)
invfile(4)=invy(112)
etc...
but when it gets to "invfile(42)=invy(367)", I just get a blank
column in the export file. invy(367) is the field containing the
(16,memo) edit.
Can someone please help me with this?
P.S. I hope this isn't going to be a re-post because I thought I
posted this a couple days ago but never saw it come across.
Mike
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<a class="moz-txt-link-rfc2396E" href="http://mailman.celestial.com/pipermail/filepro-list/attachments/20170815/7fe803a7/attachment.html"><http://mailman.celestial.com/pipermail/filepro-list/attachments/20170815/7fe803a7/attachment.html></a>
_______________________________________________
Filepro-list mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Filepro-list@lists.celestial.com">Filepro-list@lists.celestial.com</a>
Subscribe/Unsubscribe/Subscription Changes
<a class="moz-txt-link-freetext" href="http://mailman.celestial.com/mailman/listinfo/filepro-list">http://mailman.celestial.com/mailman/listinfo/filepro-list</a>
</pre>
</blockquote>
<pre wrap="">
---
This email has been checked for viruses by Avast antivirus software.
<a class="moz-txt-link-freetext" href="https://www.avast.com/antivirus">https://www.avast.com/antivirus</a>
_______________________________________________
Filepro-list mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Filepro-list@lists.celestial.com">Filepro-list@lists.celestial.com</a>
Subscribe/Unsubscribe/Subscription Changes
<a class="moz-txt-link-freetext" href="http://mailman.celestial.com/mailman/listinfo/filepro-list">http://mailman.celestial.com/mailman/listinfo/filepro-list</a>
</pre>
</blockquote>
<pre wrap="">
_______________________________________________
Filepro-list mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Filepro-list@lists.celestial.com">Filepro-list@lists.celestial.com</a>
Subscribe/Unsubscribe/Subscription Changes
<a class="moz-txt-link-freetext" href="http://mailman.celestial.com/mailman/listinfo/filepro-list">http://mailman.celestial.com/mailman/listinfo/filepro-list</a>
</pre>
</blockquote>
<br>
</body>
</html>