Just a reminder - STRTOFILE and FILETOSTR are limited by the size of a memory variable - 16,384K bytes (16,777.184 bytes).
Had to fix some software that was truncating PDF files at 16 MB... ||
|Brant Layton| |480.964.1316| On 4/25/2017 6:00 PM, profoxtech-request@leafe.com wrote:
RE: Getting count of rows in a text file -- best approach?
--- StripMime Report -- processed MIME parts --- multipart/alternative text/plain (text body -- kept) text/html ---
On 2017-04-26 12:31, Brant E. Layton wrote:
Just a reminder - STRTOFILE and FILETOSTR are limited by the size of a memory variable - 16,384K bytes (16,777.184 bytes).
Had to fix some software that was truncating PDF files at 16 MB... ||
Looked up the Visual Foxpro System Capabilities: Maximum # of characters per character string or memory variable. = 16,777,184
That seems odd. I thought I had tested with a file larger than 16 MB and gotten correct numbers?
Sure looks like you can load larger than 16MB. Though the help file does say a 16MB limit on memory variables.
Fred
On Wed, Apr 26, 2017 at 11:44 AM, < mbsoftwaresolutions@mbsoftwaresolutions.com> wrote:
On 2017-04-26 12:31, Brant E. Layton wrote:
Just a reminder - STRTOFILE and FILETOSTR are limited by the size of a memory variable - 16,384K bytes (16,777.184 bytes).
Had to fix some software that was truncating PDF files at 16 MB... ||
Looked up the Visual Foxpro System Capabilities: Maximum # of characters per character string or memory variable. = 16,777,184
That seems odd. I thought I had tested with a file larger than 16 MB and gotten correct numbers?
[excessive quoting removed by server]
On 2017-04-26 16:05, Fred Taylor wrote:
Sure looks like you can load larger than 16MB. Though the help file does say a 16MB limit on memory variables.
Fred
Perhaps the Help file is outdated? That guy from the Fox team must have been let go before he could update it. <g>
Mentioned in "Visual Foxpro system capacities"
Thierry Nivelet http://foxincloud.com/ Give your VFP app a second life in the cloud
Le 1 mai 2017 à 23:20, mbsoftwaresolutions@mbsoftwaresolutions.com a écrit :
the help file does say a 16MB limit on memory variables
It is true and yet it is not. Rick Strahl wrote an article showing there are things you can do (and not do) with HUUGE files read in using FileToStr():
https://www.west-wind.com/wconnect/weblog/ShowEntry.blog?id=882
Since the Original Poster (anyone remember him :)?) was only performing read-only functions on the file once read in, this should work.
On Tue, May 2, 2017 at 5:57 AM, Thierry Nivelet tnivelet@foxincloud.com wrote:
Mentioned in "Visual Foxpro system capacities"
Thierry Nivelet http://foxincloud.com/ Give your VFP app a second life in the cloud
Le 1 mai 2017 à 23:20, mbsoftwaresolutions@mbsoftwaresolutions.com a écrit :
the help file does say a 16MB limit on memory variables
[excessive quoting removed by server]
On 2017-05-02 06:43, Ted Roche wrote:
It is true and yet it is not. Rick Strahl wrote an article showing there are things you can do (and not do) with HUUGE files read in using FileToStr():
https://www.west-wind.com/wconnect/weblog/ShowEntry.blog?id=882
Since the Original Poster (anyone remember him :)?) was only performing read-only functions on the file once read in, this should work.
Excellent...thanks, Ted. Yes, FILETOSTR(..) worked for me. (And yes, I was the original poster. lol)
I answered to 'not documented'
Of course filetostr() works as it does not go through a variable.
Question vastly discussed on AtoutFox.
Var = "16 MB string" Var = m.var + 'n' && bingo
Thierry Nivelet http://foxincloud.com/ Give your VFP app a second life in the cloud
Le 2 mai 2017 à 12:43, Ted Roche tedroche@gmail.com a écrit :
It is true and yet it is not. Rick Strahl wrote an article showing there are things you can do (and not do) with HUUGE files read in using FileToStr():
https://www.west-wind.com/wconnect/weblog/ShowEntry.blog?id=882
Since the Original Poster (anyone remember him :)?) was only performing read-only functions on the file once read in, this should work.
On Tue, May 2, 2017 at 5:57 AM, Thierry Nivelet tnivelet@foxincloud.com wrote: Mentioned in "Visual Foxpro system capacities"
Thierry Nivelet http://foxincloud.com/ Give your VFP app a second life in the cloud
Le 1 mai 2017 à 23:20, mbsoftwaresolutions@mbsoftwaresolutions.com a écrit :
the help file does say a 16MB limit on memory variables
[excessive quoting removed by server]
Ok, who else chuckled when the database guy doesn't use data to get a count but is going to count text file lines instead?
Seriously I found that funny.
On Tue, May 2, 2017 at 9:18 AM, <mbsoftwaresolutions@mbsoftwaresolutions.com
wrote:
On 2017-05-02 05:57, Thierry Nivelet wrote:
Mentioned in "Visual Foxpro system capacities"
Yes but as Fred said, it looks like you can load greater than 16 MB. I could swear I did.
[excessive quoting removed by server]
On 2017-05-02 10:23, Stephen Russell wrote:
Ok, who else chuckled when the database guy doesn't use data to get a count but is going to count text file lines instead?
Seriously I found that funny.
It's all a matter of where you're doing the processing! Up front BEFORE you load it, showing the user "here are the files you need to load yet" or after the fact (and of course after it's loaded, this exercise is moot).
-
Brant E. Layton -
Fred Taylor -
mbsoftwaresolutions＠mbsoftwaresolutions.com -
Stephen Russell -
Ted Roche -
Thierry Nivelet