Export buffers borking?

[John Esak]

You've got worse than mad cow... the SORt() and @wbrk functions can NOT
exist on the same table. The former is only available on -v (sort/select)
tables and the latter, @wbrk, is only available on output tables.

John


> -----Original Message-----
> From: filepro-list-bounces+john=valar.com at lists.celestial.com
> [mailto:filepro-list-bounces+john=valar.com at lists.celestial.com] On Behalf
> Of Walter Vaughan
> Sent: Friday, October 12, 2007 5:51 PM
> To: filePro
> Subject: Re: Export buffers borking?
> 
> 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
> _______________________________________________
> Filepro-list mailing list
> Filepro-list at lists.celestial.com
> http://mailman.celestial.com/mailman/listinfo/filepro-list