>Not to discourage you but I already have n different versions of this (n versions was a result of search for speed) and it gets slower and slower as rowcount increases.

Which was to be expected - a huge _cliptext would at some point cause huge memory consumption. Then, Excel also needs to feed it into individual cells, convert into proper format etc. I'd expect it to grow squarely (or even exponentially slower).

>It seems to be working not bad for the first 64K records (first sheet) but then with each new sheet timing almost is doubled.

And that's pretty much the limit of what I have. I rarely get more than few thousand rows in a sheet, so this is sufficient for my needs. A sheet larger than that is pretty much unusable for human consumption. Though they do love the autofilter (which I automatically enable in the end, on my named range), so they just filter on whatever they want... I suspect that they use these sheets as database snapshots, and I don't really care if they do. It's a representation of the data that's much more user-oriented than any form I could cook up.

>PS:
>
>Copy to tempfile.txt delimited with tab
>_cliptext = FileToStr(...)
>erase tempfile.txt && Instead of datatoclip

Are you saying that _vfp.datatoclip() is also getting slower as recc() increases? Good to know.

>.Range('A1').PasteSpecial && Instead of calculating target range

I have to increase the target range because all my sheets are based on template sheets, so this pushes the total lines down for exactly as much as I need them, and the range to insert into is named - and also expands (the trick is in one extra line in the range, which I keep with a minimal height) and keeps the name throughout the process.

Thanks for the tip - if I ever run into something too big to do it this way, I'll remember it.