Thanks. I have been using the one that is listed in the DATE$ page on the wiki (http://www.qb64.org/wiki/DATE$), which has worked fine. I'm just playing around right now. My first test is at 4am tomorrow 6/26) morning. I'm just trying to make sure the basic ideas work before I add more bells and whistles. Mike

Pete, I think I will take your advice and write my own. I'm thinking on having a data file with all of the task data, that is read as soon as the task program runs. It would display the scheduled tasks and allow for adding, deleting, or modifying tasks. If any of those three are selected, the data file is updated. I would have a home screen with each of the tasks displayed, and if one of the three modification options are selected, then it would change to a screen to all of that option to be performed. When the modification option is completed, the data file is updated and you are returned to the home screen.

In trying to figure out a format for the data file, I'm thinking of using a value between 0 and 127 to be able to identify which days of the week the task is to be run. A value of 127 means every day, a value of 62 means just on weekdays, a value of 65 means just on weekends, etc.

Thoughts, Mike

My apologies to SierraKen and Bplus if this is hijacking your original post. If a new thread is best, I will certainly do it.

To Petr's post; I have four folders with video, Home Video, Movies, Video, and YouTube (I have a program that downloads stuff from YouTube). Each of these folders has subdirectories that contain avi, mp4, mpg, and mpeg files. I use VLC to play them.

As a start, I am thinking of the following tags; name of the video clip, B/W or color, length of clip, type of clip (home movie, war movie, computer tutorial video, etc.). So I believe I will certainly need a search and sort capability (bubble sort - cuz I easily understand that one!).

Mike

Pete, I have thought about that as well. I have a couple things I want to try first. I'm still working on the 'file open' errors I get randomly. I had them again today. That one is equally weird. Mike

I just got around to putting the program in a batch file and having the task scheduler execute the batch file. Same exact results. I also tried a different approach, with promising results. I use a program called Second Copy to make backup copies of my important data. One of the features of Second Copy is to run a program either before or after the Second Copy profile has run. So I put my program to run after the last profile of the night runs. It worked. Hmmm, this is really weird! Mike

I know this is probably a really dumb question; and I'm going way out on a limb here; but is there anything that gets put in a compiler QB64 .exe file that would make it not work with task scheduler? Here is the background... I wrote a program awhile back, did all the testing I needed to do, and then set up task scheduler to have it run each morning at 7:00am. No problems; works fine, lasts a long time.

So, I wrote another program that I also wanted to run at a certain time. No dice; ever. I have tried to kick it off at differing times, nothing. Set up the execution parameters the same as the one that works, nothing. The task scheduler history says that everything went fine; task triggered on scheduler, created task process, task started, action started, action completed, and task completed. All of them within one second of the start time. and the last run result shows up a 0x6F; of which I cannot find any trace of what that means.

Oh, i can run the program just fine; either by the normal double click from file explorer or selecting 'run task' from the task scheduler. Like I said, probably a dumb question, but I figured I try a longshot just in case. Thanks, Mike

Thanks Petr. I think part of my problem is that I used "GOTO Loop1" and not "RESUME Loop1". I was reading through the QuickBASIC Bible when I realized I should have used RESUME. I don't think the "file already open error" is coming from my program, since that file is only opened once in the program, and when the error occurs, it seems to be at different places in the program. The program reads about 2 dozen different files, but one at a time, and in a sequence; ie. open, read the data, close the file, manipulate the data, and then move on to the next one.

The problem occurs randomly and intermittently, and at different places in the program. Since the files begin to be read fairly quickly after the files are created (from a SHELL batch file), I am wondering if the files are flagged as opened due to the anti-virus program scanning them and they are not closed before my program wants to open and read them. I have excluded the entire folder from scanning by the AV program to see if that helps. But again, since it happens randomly and intermittently, it may be awhile before I am certain. Thanks, Mike

IN the process of putting together this program to get stock data and display it, I use wGet to retrieve the data into a file, via a SHELL execution of a batch file, then I read the data from each file into the program. Every once and awhile I get errors of each of the file. Error 55 followed by error 62.

I thought it might be that the wGet/batch created files hadn't been closed, so I added a 30 second delay after the line that executes the SHELL command (SHELL _HIDE "CMD /C MoneywGet.bat"). But that hasn't seemed to work.

I also added an error handler routine (ON ERROR GOTO Errhandler)...


But that still posts the error popups, and it never really goes back to the beginning (Loop1), it just goes and displays the next error popup. Any thoughts on what I am doing wrong; or missing? Thanks, Mike