<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Now I'm wondering if anyone knows of limitations in a SLK file</p>
<p>Just messing around I was trying this <font size="+1"
color="#3333ff">aa(255,*)=""{invy(367){""</font> with different
field lengths. When aa=255 it exports the data to the slk file but
as soon as I changed it to 256 I get the errors and nothing
exported.</p>
<p><br>
</p>
<p>Mike<br>
</p>
<br>
<div class="moz-cite-prefix">On 8/17/2017 2:11 AM, Mike Fedkiw
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:7d1fa81b-a157-fe15-f255-46d2f354770b@gmail.com">Well
after everything I've been through trying to get the MEMO field to
export it's looking like I'm back to the start or almost.
<br>
<br>
I was kinda happy when I was able to export the MEMO field to a
CSV file, it actually looked okay. That was only with about 20 or
so records though, but when I exported my entire inventory file it
was a different story all together.
<br>
<br>
It didn't matter if I opened the CSV with excel or if I imported
the data into an xls file defining all the columns, it was a mess
with columns shifted all over the place. SLK files don't have this
issue at all, they open just like an xls file to manipulate
whatever is needed and afterwards I can simply save it as a CSV to
import into whatever.
<br>
<br>
So... it's looking like tomorrows project is going to be messing
with this XLATE example from Bruce to see if I can get the MEMO
exported into an SLK file without the errors that I've been
getting.
<br>
<br>
Filepro, making a simple processes miserable at times, ugh
<br>
<br>
<br>
Mike
<br>
<br>
<br>
<br>
<br>
On 8/16/2017 2:21 PM, Bruce Easton via Filepro-list wrote:
<br>
<blockquote type="cite">Bill Randall wrote earlier with this:
"Note the syntax for handling memo fields is a little different
than regular fields. When assigning it, precede it with {""
<br>
<br>
<br>
I've never used this technique - most likely because the memo
fields
<br>
I've worked with had more data geared for a memo field - i.e.
text
<br>
with embedded newlines for instance, and in addition, more
<br>
interpretation or selection was desired within the memo field
data for
<br>
the output assignment. Therefore, my examples all required
memo
<br>
export followed by reading of the memo exported data line by
line to
<br>
achieve interpretation and selection. So it's good to know
that for
<br>
certain purposes - a simple assignment from the memo field will
do the
<br>
trick.
<br>
<br>
What I just discovered, though, is that even with a memo field
of one line, even after:
<br>
<br>
export MULTI expfld=(outputfile)
<br>
<br>
expfld(1)=""{memofield{""
<br>
<br>
that the exported data still contains an end of line character
after the exported memo field data before the close double-quote
for that field. As Mike pointed out, Excel can handle this for
csv, but gives errors when opening .SLK files.
<br>
<br>
Therefore, this works for me under Linux to correctly format the
.SLK file for Excel:
<br>
<br>
Then: aa(20,*)=""{memo_fld{""
<br>
Then: ab(20,*)=xlate(aa,chr("10"),"") 'get rid of new lines
<br>
Then: export MULTI outf=("/tmp/betest.slk")
<br>
Then: outf(1)=ab
<br>
<br>
On Windows for this, I'm not sure if you would also need to
xlate out any carriage returns (chr("13")).
<br>
<br>
Bruce
<br>
<br>
<br>
<br>
On 8/16/17 12:56 PM, Mike Fedkiw via Filepro-list wrote:
<br>
<blockquote type="cite">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>
*
<br>
invfile(42)=invy(367) [did NOT work]**
<br>
**invfile(42)=""{invy(367) [DID WORK]**
<br>
**invfile(42)=""{invy(367){"" [DID WORK]
<br>
<br>
**The above was when exporting the MEMO field as WORD/CSV, not
SLK*
<br>
<br>
*Now if I could only get this to export to a SLK file I'd be
golden, ugh*
<br>
<br>
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)".
<br>
<br>
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>
<br>
I just realized now that it was reporting the exact number of
errors as records containing that contained MEMO's.
<br>
<br>
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>
<br>
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.
<br>
<br>
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>
<br>
Mike
<br>
<br>
<br>
<br>
<br>
On 8/16/2017 11:10 AM, Faisal Karim wrote:
<br>
<blockquote type="cite">Have you tried?
<br>
<br>
invfile(42)=""{invy(367){""
<br>
<br>
Faisal
<br>
<br>
-----Original Message-----
<br>
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
<br>
Sent: Tuesday, August 15, 2017 6:17 PM
<br>
To: Bruce Easton; 0 Filepro List
<br>
Subject: Re: exporting MEMO along with other data
<br>
<br>
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.
<br>
<br>
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.
<br>
<br>
I'm doing a sub routine to export the MEMO field but nothing
works, examples below.
<br>
<br>
=======================================================
<br>
<br>
expmemo◄ If:
<br>
Then: MEMO invy(367) EXPORT "memo"
<br>
<br>
=======================================================
<br>
<br>
expmemo◄ If:
<br>
Then: MEMO invy(367) EXPORT "memo.txt"
<br>
<br>
=======================================================
<br>
<br>
expmemo◄ If:
<br>
Then: MEMO invy(367) EXPORT "c:\memo"
<br>
<br>
=======================================================
<br>
<br>
expmemo◄ If:
<br>
Then: MEMO invy(367) EXPORT "c:\memo.txt"
<br>
<br>
=======================================================
<br>
<br>
Some just got the above got stuck on a black screen, some
caused memory errors, etc...
<br>
<br>
Can someone give me an example, any example of exporting a
memo field into a file?
<br>
<br>
I just hoping the readline stuff will be easier to do
because I've never had to use that for anything either.
<br>
<br>
<br>
Mike
<br>
<br>
<br>
On 8/15/2017 1:39 PM, Bruce Easton via Filepro-list wrote:
<br>
<blockquote type="cite">Mike - the 'memo xx export...'
command line should export the data
<br>
from the memo field to the destination you specify in that
command.
<br>
It is then up to you to read that resulting memo-exported
file so that
<br>
you can then output the data as desired in your 'invfile'
export file.
<br>
<br>
In place of "invfile(42)=invy(367)", you may want to have
a 'gosub
<br>
getmem, where that subroutine would:
<br>
<br>
1. export the memo field
<br>
2. read the exported memo field file from step 1 (for
instance, using
<br>
readline loop)
<br>
3. massage/select_from the data read in step 2 in order
to:
<br>
4. then assign to invfile(42) what you need there
<br>
<br>
On 8/15/17 12:48 PM, Mike Fedkiw via Filepro-list wrote:
<br>
<blockquote type="cite">windows server 2008 r2,filepro
5.0.05dn9
<br>
<br>
The line below is what I've been using to export the
selected fields
<br>
information into a file. It's been working pretty good
now, at least
<br>
until it gets to the field containing the memo which
always winds up
<br>
to be a blank column.
<br>
<br>
export multi invfile=c:\!Output\eBay\eBayInvy.slk
<br>
<br>
In the help I see this...
<br>
<br>
"MEMO xx EXPORT filename Exports the MEMO field xx to
the
<br>
specified filename"
<br>
<br>
From that I have no clue how to get it to do what I'm
needing as far
<br>
as the memo.
<br>
<br>
I've got a ton of fields currently being exported into
this file
<br>
which all work just fine like...
<br>
invfile(1)=invy(1)
<br>
invfile(2)=invy(14)
<br>
invfile(3)=invy(68)
<br>
invfile(4)=invy(112)
<br>
etc...
<br>
but when it gets to "invfile(42)=invy(367)", I just get
a blank
<br>
column in the export file. invy(367) is the field
containing the
<br>
(16,memo) edit.
<br>
<br>
Can someone please help me with this?
<br>
<br>
P.S. I hope this isn't going to be a re-post because I
thought I
<br>
posted this a couple days ago but never saw it come
across.
<br>
<br>
Mike
<br>
<br>
<br>
<br>
-------------- next part --------------
<br>
An HTML attachment was scrubbed...
<br>
URL:
<br>
<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>
<br>
_______________________________________________
<br>
Filepro-list mailing list
<br>
<a class="moz-txt-link-abbreviated" href="mailto:Filepro-list@lists.celestial.com">Filepro-list@lists.celestial.com</a>
<br>
Subscribe/Unsubscribe/Subscription Changes
<br>
<a class="moz-txt-link-freetext" href="http://mailman.celestial.com/mailman/listinfo/filepro-list">http://mailman.celestial.com/mailman/listinfo/filepro-list</a>
<br>
<br>
</blockquote>
<br>
<br>
---
<br>
This email has been checked for viruses by Avast antivirus
software.
<br>
<a class="moz-txt-link-freetext" href="https://www.avast.com/antivirus">https://www.avast.com/antivirus</a>
<br>
<br>
_______________________________________________
<br>
Filepro-list mailing list
<br>
<a class="moz-txt-link-abbreviated" href="mailto:Filepro-list@lists.celestial.com">Filepro-list@lists.celestial.com</a>
<br>
Subscribe/Unsubscribe/Subscription Changes
<br>
<a class="moz-txt-link-freetext" href="http://mailman.celestial.com/mailman/listinfo/filepro-list">http://mailman.celestial.com/mailman/listinfo/filepro-list</a>
<br>
</blockquote>
_______________________________________________
<br>
Filepro-list mailing list
<br>
<a class="moz-txt-link-abbreviated" href="mailto:Filepro-list@lists.celestial.com">Filepro-list@lists.celestial.com</a>
<br>
Subscribe/Unsubscribe/Subscription Changes
<br>
<a class="moz-txt-link-freetext" href="http://mailman.celestial.com/mailman/listinfo/filepro-list">http://mailman.celestial.com/mailman/listinfo/filepro-list</a>
<br>
</blockquote>
<br>
-------------- next part --------------
<br>
An HTML attachment was scrubbed...
<br>
URL:
<a class="moz-txt-link-rfc2396E" href="http://mailman.celestial.com/pipermail/filepro-list/attachments/20170816/e8fe23b0/attachment.html"><http://mailman.celestial.com/pipermail/filepro-list/attachments/20170816/e8fe23b0/attachment.html></a><br>
_______________________________________________
<br>
Filepro-list mailing list
<br>
<a class="moz-txt-link-abbreviated" href="mailto:Filepro-list@lists.celestial.com">Filepro-list@lists.celestial.com</a>
<br>
Subscribe/Unsubscribe/Subscription Changes
<br>
<a class="moz-txt-link-freetext" href="http://mailman.celestial.com/mailman/listinfo/filepro-list">http://mailman.celestial.com/mailman/listinfo/filepro-list</a>
<br>
</blockquote>
<br>
<br>
-------------- next part --------------
<br>
An HTML attachment was scrubbed...
<br>
URL:
<a class="moz-txt-link-rfc2396E" href="http://mailman.celestial.com/pipermail/filepro-list/attachments/20170816/a615bfcc/attachment.html"><http://mailman.celestial.com/pipermail/filepro-list/attachments/20170816/a615bfcc/attachment.html></a><br>
_______________________________________________
<br>
Filepro-list mailing list
<br>
<a class="moz-txt-link-abbreviated" href="mailto:Filepro-list@lists.celestial.com">Filepro-list@lists.celestial.com</a>
<br>
Subscribe/Unsubscribe/Subscription Changes
<br>
<a class="moz-txt-link-freetext" href="http://mailman.celestial.com/mailman/listinfo/filepro-list">http://mailman.celestial.com/mailman/listinfo/filepro-list</a>
<br>
</blockquote>
<br>
</blockquote>
<br>
</body>
</html>