# Network drive not available when the FTP script is scheduled

21st July 2018

As all Windows applications, ScriptFTP supports the use of UNC paths and network drives. You can use the files and folders stored in them as if they were located in hard drive of the machine where ScriptFTP is running. For instance:

# Upload to the FTP server all the Excel files stored in the mapped network drive Z
PUTFILE("Z:\the_folder\*.xlsx")

# Upload to the FTP server all the Word documents stored in a network share called Reports
# under the computer named ACCOUNTING-PC-1
PUTFILE("\\ACCOUNTING-PC-1\Reports\*.docx")

# How to set a FTP script to be run every X minutes

30th May 2017

From time to time a question like this is received in the tech support inbox:

I wanted to ask if you can set the sheduler every minute, thank you so much

In this case, the answer is straight: using the Windows task scheduler. Let’s see step-by-step how to configure it to run a FTP script every 1 minute:
1.- First, we create the scheduled script under ScriptFTP. This is a shortcut that will create for us a scheduled ScriptFTP task in the Windows task scheduler. We can also open directly the Windows the windows task scheduler and create the task manually but we will have to enter the ScriptFTP.exe path, the script path etc. Using ScriptFTP for this is easier:

# A dump of random common questions

18th January 2017

I would like to obtain the encryption tool.

How can i start a scheduled task every hour at XX:55 and at startup of scriptFTP

You need to create a scheduled task within ScriptFTP and then open the windows task scheduler (usually under the control panel). Once you have located that task in the windows scheduler, open it and go to the “Triggers” tab. There you have to schedule the task to be run daily at, for instance, 00:55 and to be repeated every hour for one day.
To run a script file at the ScriptFTP startup you need to create a shortcut in windows that calls ScriptFTP wiith these parameters:

C:\Program Files(x86)\ScriptFTP\ScriptFTP.exe "C:\the_path\to_my_script\the_script_file.ftp"

# Handling file dates and time spans

13th December 2016

The ScriptFTP scripting language does not have data types (as most scripting languages) and dealing with anything which is not plain text requires some kind of tricks. This happens with file lists as we have seen before, dates and time spans suffer the same limitation. This post covers how these data types are handled in ScriptFTP.

# How to run a scheduled FTP script in the background

16th November 2016

The ScriptFTP integrated scheduler is used to set a script to be run at given times. Once a script is scheduled the Windows Task programming service will automatically launch ScriptFTP.exe with the appropiate parameters and a window will pop-up in the user desktop and do the file transfer. Some users find this annoying and want the FTP script to be run in the background. This post covers this issue.

# A note about the script to EXE conversion service

7th January 2015

From time to time we receive an email asking if the script to EXE conversion service (more info about it here) is an installable software, or a Windows service that runs in the background and automatically converts the FTP files to standalone EXE programs.

Well, it is not. This is a special kind of customer service where we manually build an EXE file (using the Windows development tools) from a script file you send to us. It is that simple ;).

# A question regarding how to share parameters between many script files

13th December 2014

I would like to share here a common question that from time to time it is answered via email (you can request tech support in the Contact section):

Dear Support:

Sorry to bother you, I looked at a few forum pages and could not search for ‘include’ (because it was ‘a too common word’).  Just a high-level question in three parts as I am evaluating ScriptFTP:
1) Can I use the equivalent of an ‘#include <stdio.h>’ (C notation) to put common parts of scripts or functions into one place?  All the examples I have seen were in one stand-alone ‘.ftp’ file.
2) If not possible, can I at least make a connection script that I call from another script and use it?
(For example on.ftp is the logon and off.ftp the logoff script, can I have a main.ftp that calls on.ftp, does some FTP stuff and calls off.ftp then?)
3) If 2) works, could I call the three .ftp scripts from a Powershell individually (in sequence)?  Or do I lose the connection as soon as the script is done?

So far I am impressed.  The scripting is easy and straightforward, and from what I’ve read I can combine it with Powershell via command line… The best feature is the return code check after each command during the session.  Good job.