CuteFTP Professional User s Guide 

  MySite.Option ("ThrowError") = True 

  MySite.Host = "ftp://user:pass@myftpsite.com"  one of 

the ways to connect using the TE 

  MySite.Connect 

  MySite.Upload "c:\archive.zip"  upload the new archiv ,

e  

then check to see if it made it up to the server. 

  if not CBool(MySite.RemoteExists("\archive.zip")) the  

n

   MsgBox "Failed to Upload, Exiting!" 

  Else 

     MsgBox "Success!" 

  End If 

  MySite.Disco n

n ec  

t

  MySite.Close 

Else 

MsgBox "Compression and Encryption Failed, Exiting!" 

End If 

Note: 

You can optionally protect the FTP login by connecting with SSL, SSH2 

or OTP using CuteFTP Professional s Transfer Engine (GlobalSCAPE s 

Secure FTP Server 2 supports SSL, OTP, and SSH2 logins). Use the 

protocol property to set the connection type prior to calling MySite.Host 

and MySite.Connect. 

R

UNNING THE 

T

RANSFER 

E

NGINE FROM AN 

SQL 

JOB

You can use SGL function sp_OACreate to create a TEConnection object. SQL runs ftpte 

and hides all windows. SQL uses a special instance of ftpte exe, wh c

i h cannot prompt for 

user name and password.  

Specify a local download path or filename. While optional, it s a good idea to make sure that 

it is going where you intend. Also, make sure that the local path has the appropriate NTFS 

permissions to allow the TE to have full control. 

For scripted or scheduled tasks use an otherwise unused account for scheduled TE tasks. 

Once the CuteFTP TE (transfer engine) is started,  n

a other instance cannot be created. 

Windows treats the logged in user differently than the logged out user and DCOM errors 

may occur. For instance, if a

   recurring background process has already run before the user 

logs in, once the user logs in and the background process starts again, a DCOM error will 

occur. 

Example transfer script 

DECLARE @property varchar(255) 

DECLARE @object int 

232