Hey Jim, Yea you could be right!
I do believe that creating it locally and moving to the network drive can be more efficient. I’m not sure how much speed different there would be. > using TEXT TO BLOB with the offset parameter I’m investigating this command and seeing if I can understand how to use it. I’ve only used/seen this command in Tony’s R. BB_Decrypt/BB_Encrypt methods. Nothing in the KB that I can find with a real world example. Anyway, I think that’s a road I have to go down. Appreciate, John… > On Apr 15, 2020, at 1:25 PM, James Crate <j...@quevivadev.com> wrote: > > In the time it takes to troubleshoot this, you could probably rewrite the > report to be much faster and more reliable. > > I would start by writing the file to a local temp file, and then copying that > file to the network drive when finished. This reduces the impact of network > issues both for completing the operation and the network share, and makes it > much more likely you only get a completed version on the network share for > external consumption. > > The fastest way to build the output is probably with a pre-sized blob, and > using TEXT TO BLOB with the offset parameter. Pushing elements into a > collection and then using collection.join() is also pretty fast, but again > you’d have to test to see how large a text variable can actually be, and > whether the limit was large enough both interpreted and compiled. If you > don’t have enough RAM for a 1GB blob, smaller blobs may work with SEND PACKET. > > Jim Crate ********************************************************************** 4D Internet Users Group (4D iNUG) Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:4d_tech-unsubscr...@lists.4d.com **********************************************************************
