Sage 100

I need to sFTP some files down from a server prior to the VI import. Has anyone been successful in scripting that from inside of the visual integrator. (Via a batch file or Perform logic). Also I need to run these programs on the server not from the client.

Try psftp from the same guys who make PuTTY. http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html You should be able to run it from the command line.

I had been trying coreftp but the client wasn't starting from the inside VI via a dos batch. I will give it a go.

@JimWoodhead - I think we had a thread about this a few months ago with standard ftp from a batch file. I think most of that would apply except you need the psftp.exe that comes with PuTTY ( as Aaron said while I was typing this) and replace put with get.

I believe that is what we used as well for a client who ftp's their POS to us nightly. Our DOS batch script then kicks off a ton of VI jobs. Not sure if we trigger the FTP or the client does on their side.

Another way might be dropbox?

I need to do it within the vi so it all runs on the server. I am going to call it from a XenApp client. Jim

Wayne's idea is not bad if it has the same functionality as Sharefile. We can setup an autosync to run on a schedule and then have the batch file timed to run after that.

You could use the ftp client that is built into windows and it can be run from a batch file while taking commands from a text file. Here is what an ftp transfer.scr file might look like: user ntuser d#ntpr0suser cd MySQL_Update lcd FromAccessApp get AP1_VendorMaster.csv get Customer_List.csv The command in a batch file would be: ftp ftp.somedomain.com -s:transfer.scr Transfer logs into ftp.somedomain.com as user ntuser with password d#ntpr0suser, changes to the directory MySQL_Update on the ftp server and the FromAccessApp on the local machine, then gets two files. The batch file can be run by the VI job,

I reread the requirements - must be secure FTP.

While I haven't done this from a script, I do use Core FTP (coreftp.com) to facilitate the transfer. You'd configure Core FTP with credentials and use command line parameters in a batch file to initiate transfer. The batch file can be launched from VI to perform on Job Start. Else, code everything into the batch file... ftp command (using Core FTP), as well as the VI job itself.

I have had success running a job such as this from a batch file as well. Although in my case I am exporting data and then 'ftp'ing to a site, the concept is the same. This has the added advantage of allowing me to use windows scheduler to fire the whole thing off.

#Just reading over this. I was able to script it via coreftp (le). Works great.

Yeah. @MyronStevenson is good for something occasionally.