Export buffers borking?

[Walter Vaughan]

Fairlight wrote:

> I really hate it when programs don't actually say what they mean.  It's
> -not- out of memory.  There's plenty of memory left.  It's a buffer
> overflow condition--albeit one that's handled gracefully and NOT the
> security-type buggy one.
> 
> You see "out of memory", you start looking at a far different set of
> potential remedies than you do if you see another message. 

Actually it bit me again this morning, and what was making me crazy was that I 
was getting random results or out of memory. I ended up fixing it by manually 
clearing a "old fashioned" dummy field and writing the export per record.

The random result came from:
I've been spending a lot of time around SQL and I thought I could do something 
like this in a -v table....

         sort1=1{6;end
@wbrk1
         select;end

of course my mind was thinking select distinct and I just want the last record 
so I have to select it when I break :) of course that's not the filePro way to 
do it.

I've got mad cow you know....

--
Walter