FilePut request

Started by bottomleypotts, June 28, 2025, 07:04:35 AM

Previous topic - Next topic

bottomleypotts

Using fileput with onedrive can sometimes cause my apps to crash. I notice it when I'm debugging an app and I'm rapidly dumping stuff into a file. I don't suppose we could have an option like fileopen does where it waits or times out, rather than crashes?

spl

Seems like an issue for error-handling. just .02
Stan - formerly stanl [ex-Pundit]

bottomleypotts

I didn't say that I cannot code error handling. I made a request. Much the same way that Fileopen was improved in 2007 to include the timeout function.

spl

Quote from: bottomleypotts on June 29, 2025, 03:21:10 AMI didn't say that I cannot code error handling. I made a request. Much the same way that Fileopen was improved in 2007 to include the timeout function.

Well sir, under the agree to disagree apron, your request is based on a 'sometimes' happens and not a lot of other users have the same issue - hence an upgrade for a WB internal might not be in the best interest. But I must mention that years ago when my WB scripts had issues with SQL updates, inserts and even queries where at the time the script would fail, I asked similar questions. The answer was the addition of a P3 in IntControl(73...  to create a UDS to handle a situation should it arrive. Found it gave me the opportunity to learn more about SQL failures while keeping a script intact. I would suggest for your situation you look into the P3 UDS and possibly come up with a fileput() error handler for particular situations. Again just .02
Stan - formerly stanl [ex-Pundit]

snowsnowsnow

You are confusing "I think the WB devs should do this" with "Please help me fix my script and solve my personal problem(s)".

They are not the same thing.

Now, you may not like the sentiment expressed in the first version above, but let's not play dumb and deny that it exists.

td

Quote from: bottomleypotts on June 28, 2025, 07:04:35 AMUsing fileput with onedrive can sometimes cause my apps to crash. I notice it when I'm debugging an app and I'm rapidly dumping stuff into a file. I don't suppose we could have an option like fileopen does where it waits or times out, rather than crashes?

What do you mean by "rapidly dumping stuff"? Are you getting error 1800 or error 1802? If you are receiving error 1800, try placing a TimeDelay of .5 seconds or whatever between calls to FilePut and report the results here.
"No one who sees a peregrine falcon fly can ever forget the beauty and thrill of that flight."
  - Dr. Tom Cade

bottomleypotts

Quote from: td on September 19, 2025, 03:33:18 PMWhat do you mean by "rapidly dumping stuff"? Are you getting error 1800 or error 1802? If you are receiving error 1800, try placing a TimeDelay of .5 seconds or whatever between calls to FilePut and report the results here.

I'm interacting with websites. Sometimes I rapidly create debug info using fileput. It appears Microsoft have addressed the issue because I cannot repeat it at the moment.

As I have already said, I have error handling to solve the problem. But just as a timeout was added to FileOpen I figured I would ask for the same to on FilePut.

td

The reason I asked the question is that adding a FileOpen timeout to FilePut may not solve your issue. It all depends on the cause. For example, the error may occur during file transfer, rather than during the process of opening the file.   
"No one who sees a peregrine falcon fly can ever forget the beauty and thrill of that flight."
  - Dr. Tom Cade

bottomleypotts

Quote from: td on September 20, 2025, 08:39:02 AMThe reason I asked the question is that adding a FileOpen timeout to FilePut may not solve your issue. It all depends on the cause. For example, the error may occur during file transfer, rather than during the process of opening the file.   

Gotcha. Makes sense. Will keep an eye out for it happening again and report back if it does.

SMF spam blocked by CleanTalk