GS wrote:
I have also found the following:
1) one does not have to use FreeFile for a file number (when all else
is OK).

True, however not considered 'best practice'. Freefile() ensures a
unique ID is assigned to your var.

2) cannot use "contents" for string storage space.
Why not? It's not a VB[A] keyword and so qualifies for use as a var.
* Get run-time error 458, "variable uses an Automation type not
supported in Visual Basic".



3) one cannot mix use of "/" and "\" in a string for a given file name.

Not sure why you'd use "/" in a path string! Forward slash is not a
legal filename/path character. Backslash is the default Windows path
delimiter. If choosing folders, the last backslah is not followed by a
filename.
I note that in Windoze, that "\" is used,and on the web, "/" is used.


4) one cannot have a space in the file name, so that gives a serious
problem for some web URLs (work-around anyone?)

Web paths 'pad' spaces so the string is contiguous. I believe the pad
string is "%20" OR "+".
Yes; "%20" is used and seems to act like a space and seems to kill
the URLDownloadToFile function usefulness.


5) method fails for "https:" (work-around anyone?)

What method?
* the function URLDownloadToFile. Is "method" the wrong term?