Designing a sub system, would appreciate opinions and possible solution

[mbmonk]

Hello everyone I am trying to come up with a plan to solve this problem.

Problem: A file will be uploaded, by a third party, to a remote FTP server without notifying me. I need to look for/receive these file in a timely manner ( every ten minutes for example). I would like to have this be completely automated (aka no human interaction necessary).

Network Structure: We have a server on our LAN that holds the database. We have roughly 27 clients that are networked to the server and use the database.


Horrible Solution #1 - Form Timer Event
I could try a form timer to initiate the checking of the FTP server.

Pros:
1) I think I could successfully implement it.

Cons:
1) 27 clients checking the FTP server at different times would cause unnecessary stress on the remote FTP.
2) Possible synch problems with 27 clients trying to download the files


Horrible Solution #2 - Server Overlord App

Create a new application that would only run on the server. And use it to check the FTP server every 10 minutes.

Pros:
1) Removes all they sync issues and having to manage clients.
2) Once the overlord app is in place I could use to handle other problems.

Cons:
1) If the overlord app dies, How will we know that? If it is down for more than an hour my company could lose money because of it.
2) A little more challenging to maintain two seperate apps ( overloard app and our normal client app).
3) I am not even sure I can do this. I am just thinking it should be possible.

Thoughts on these solutions or a solution I haven't mentioned?

Please let me know if I can provide more information that would help.

Thanks,
Mike Monk

[Tom Henkel]

Re: Designing a sub system, would appreciate opinions and possible solution

Mike,

We run a number of jobs unattended on our server nightly and over the weekends. Clean-up and postings, etc. The chances of the "overlord" app dieing is fairly slim, I would expect. We trigger our late night apps with a scheduling program called "Launchpad". It has a schedule component, and when the time arrives, the Alpha job is triggered, and when done, it closes, reducing overhead on the server. I don't see why this type of solution wouldn't work for you.

A second thought is to leave an app up on the server and within that app, just run a script_schedule() that would fire up a script to do your FTP processing.

Tom

[martinwcole]

Re: Designing a sub system, would appreciate opinions and possible solution

Along the same lines as Tom, a client of mine at a small hospital chain has one computer on the LAN that is dedicated for maintenance. It loads a different ADB from other users, but on the same files. It performs certain operations every four hours and every night. Also, when there are issues on the network, as index issues for example, a supervisor can go to that computer and has tools for repairing, etc.

I use Alpha's script scheduler, and the ontimer event for the Master Menu on the dedicated PC.

[mbmonk]

Re: Designing a sub system, would appreciate opinions and possible solution

Just wanted to thank you gentleman. I didn't know about the script scheduler function. I will definately look to utilize it.

Thanks again gentleman for explaining your solutions. It has really helped me get an idea of WORKING, real world solutions.