GS wrote:
After looking at your link to p5, I see what you mean by the amount of
storage space, but filename is not a factor. Parsing will certainly
downsize each file considerably...

One has to open the file to parse, so that is not logical.
The function URLDownloadToFile gives zero options - it copies ALL of
the source into a TEMP file; one hopes that the source is not equal to
or larger than 4GB in size!

For pages on the web, that is extremely unlikely; webpage size max
limit prolly is 10MB; maybe 300K worst case on the average.

So, once in TEMP, it can be opened for input (text), for random (may
specify buffer size), or for binary (may specify buffer size).
Here,one can optimize read speed VS string space used.

GS wrote:
After looking at your link to p5, I see what you mean by the amount
of
storage space, but filename is not a factor. Parsing will certainly
downsize each file considerably...

One has to open the file to parse, so that is not logical.
The function URLDownloadToFile gives zero options - it copies ALL
of the source into a TEMP file; one hopes that the source is not
equal to or larger than 4GB in size!

For pages on the web, that is extremely unlikely; webpage size max
limit prolly is 10MB; maybe 300K worst case on the average.

So, once in TEMP, it can be opened for input (text), for random
(may specify buffer size), or for binary (may specify buffer size).
Here,one can optimize read speed VS string space used.

Your last statement contradicts your first statement. Sounds like you
need to do some *extensive* research into standard VB file I/O
procedures and general parsing techniques!

--
Garry

Free usenet access at http://www.eternal-september.org
Classic VB Users Regroup!
comp.lang.basic.visual.misc
microsoft.public.vb.general.discussion

---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus

GS wrote:
GS wrote:
After looking at your link to p5, I see what you mean by the amount of
storage space, but filename is not a factor. Parsing will certainly
downsize each file considerably...

One has to open the file to parse, so that is not logical.
The function URLDownloadToFile gives zero options - it copies ALL of
the source into a TEMP file; one hopes that the source is not equal to
or larger than 4GB in size!

For pages on the web, that is extremely unlikely; webpage size max
limit prolly is 10MB; maybe 300K worst case on the average.

So, once in TEMP, it can be opened for input (text), for random (may
specify buffer size), or for binary (may specify buffer size).
Here,one can optimize read speed VS string space used.

Your last statement contradicts your first statement. Sounds like you
need to do some *extensive* research into standard VB file I/O
procedures and general parsing techniques!

Perhaps you have some things confused.
In that program, "tmp" is a string used for the name of a (hopefully)
to-be created file.

THAT file can be large,as it MUST "hold" the contents of the URL
being transferred.

Like i said, the function URLDownloadToFile gives zero options - it
copies ALL of the source into a TEMP file (named via "tmp").

Then and only then one can do I/O. I am an expert on on file I/O and
parsing; read backwards, read (and parse) TEXT files using the file in
binary or random mode; "inserting" and/or "clipping" stuff into/out of
the middle of a file, etc. When pressed, i could even write a file
backwards, but i have yet to see any reason to try that.