would you by any change trying to move a source file after a VI job?

This is from a script I have... not sure if it will work with a button.

sFTPDirCommand = "%comspec% /c TriggerFTPDirectory.bat"

Set oShell = CreateObject("Wscript.shell")

oShell.Run sFTPDirCommand, 0, true

...but if you are just moving files, why use a batch file for that?

Set objFSO = CreateObject("Scripting.FileSystemObject")

objFSO.MoveFile inFile, inFile & ".DONE"

Hi Big Louie,

No, I am trying to SFTP a file to a site.

The batch file works fine when I run it manually.

Regards,

Hi Kevin,

I'll give it a shot. 

No, i am not copying but thanks for the command, i am sure i will need to do that.

Regards,

Thanks Kevin, that worked.. !!

Regards

Does the user who is clicking on the button need to have admin rights in order for the script to run?

Not the script, but I am not sure about what the permission considerations are for the .bat file.  For a server side script I assume it would run under the context of the service login, but I am not sure on that.

If running Advanced and the script is set to execute on the server, the account running the service (whether as an application or service) would need the appropriate NTFS permissions to access the folders. If the folder is a network share or referenced via UNC, the sage 100 application server must be ran under a domain account with appropriate NTFS permissions, you can not run the service under Local System.

If Standard, the windows user running sage 100 needs to have appropriate NTFS permissions.