A5_DownLoadFile() revisited

[CALocklin]

Re: A5_DownLoadFile() revisited

If you use table.persist() before a5_DownLoadFile():
a-What good will that do? according to you, a5_DownLoadFile closes the table,

<tbl_pointer>.persist() keeps the table open so that neither of the download commands, A5_DownLoadFile() or HTTP_Download(), will close it. I though this was obvious from my previous post. Without the "persist" command, both of those download commands will close the table - but only on some systems according to Selwyn.

b-When and how are you going to close the table?

Just like I always do. With <tbl_pointer>.close(). Or, as Tim said earlier, "I used persist() after the table open. and it stayed open till I used close()"

If you put it in the loop after a5_DownLoadFile(), the table will remain open for the first loop only.

I'm not sure what the "it" is that you are referring to. If you are talking about putting the "persist" command after the download command, telling it to "persist" after it's closed won't do much good. The persist() command has to be issued before the loop starts.

If you are talking about putting a <tbl_pointer>.close() command inside the loop - you wouldn't do that in any other loop so why do it in this case? Wait until you are actually done using the table, then issue the .close() command. That could be immediately after the loop or, depending on what the table is used for, way past the end of the loop.

Has anyone tested any of these scenarios? or are all of these just abstract thinking?
Quite frankly, I am in no mood to test any of these theories as it doesn't do me any good nor do I have the time, but for any one who cares, I suggest puttng these theories to test.

Of course I've tested this. I usually test all new ideas before I post them. If not, then either I say they haven't been tested or else they aren't new to me. I try not to post solutions unless I'm at least 99% sure they will work. And, yes, it took a long time to test - probably a whole minute or so since it was a simple modification of the sample app posted above. I can guarantee you've spent far more time writing responses to this thread than I did testing the .persist() command.

Can I say this solution, or any other, will work in every situation? No, but I can say it worked on my system in the situation described.

[G Gabriel]

Re: A5_DownLoadFile() revisited

Cal:
It might shock, but I already knew what you have just said, except there is one little problem. The help file says:

The <TBL>.PERSIST() method can keep the table open after the script ends, so that a subsequent script can access the table without the overhead of having to open it again.

How does that fit into keeping the table open while the script is run? and
If it keeps the table open after the script is run, then I repeat my question, how will you close the table? Are you going to run a different script that access and closes the table? or all of this is simply an unusual use of the function? sometimes that works.

[enstorms]

Re: A5_DownLoadFile() revisited

My experience using both a5_downloadfile() and http_download(). What I do is zip my app and then upload to my webserver. Then I am able to use either of these methods to download the zip from within my app, but ONLY if I hard code the "Taget_File". I have tried every which way to create a variable and use it instead of the hard code. I have gotten it to work very rarely.

if a5.Get_Master_Path() = "" then      'if not a shadowed database
    datapath = a5.Get_Path()
else
    datapath = a5.Get_Master_Path()    

I then use:   s_quote(datapath) for the Target_File.
end if

But, as I said, it worked once or twice, but no more. It goes thru the motion, i.e. showing filename, percent downloaded, etc. but the file isn't really being downloaded unless I hardcode the Target_File.

Have also tried:

myvar = ui_get_path(.............)

Then combine myvar+filename and s_quoted it for the Target_File. It worked once.
Any ideas???
Ernie

[gmeredith17]

Re: A5_DownLoadFile() revisited

G- I think Cals's application of the table.persist() is not what it was intended for and reading the help file you would have doubts about it working. Without knowing whats under the hood for the .persist() and the download commands it is impossible to explain why it is working but it appears it does.

One possible theory is that the a5_downloadfile() function is being interpreted as a different script rather than being part of the current one. This still wouldn't really make sense but...

My preferred theory is that the A5_downloadfile() uses an in-built script for closing the open tables as the help file says when a script ends it will usually automatically closes any open tables. I think the table.persist() might stop that in-built script from activating and therefore resulting in the A5_downloadfile() not closing the table.

If you actually use the table.close() function it will override the table.persist().

I would still be of a mind to store this one under Cals's 'scary to use category' but when needs must.