×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
I think Jeff Davis hit the nail on the head, though I haven't tested. In my
Stmf_writeln() procedure, I'm writing one line at a time. I should probably
do some buffering and write it out in chunks, but I haven't updated it yet.
I know a lot of people have had issues with CPYxxIMPF, but I've never had a
problem. At least never a problem on 5.4 or higher.
Oh, and yes I leave ALL the resources open until the table is completely
read though. I might end up trying the SQL view approach though. That might
end up working better for me than my READE that I'm doing now.
--
James R. Perkins
http://twitter.com/the_jamezp
On Mon, Nov 16, 2009 at 12:33, Lim Hock-Chai
<Lim.Hock-Chai@xxxxxxxxxxxxxxx>wrote:
Is the IFS file remain open for all subsequent calls to the subprocedure
that writes data to the ifs file? It is hard to believe that your home
grown code can't beat CPYTOIMPF.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
