Events generated by the XceedFtp control represent activities that your program can recognize and act upon. For example, the Disconnected event is triggered when an FTP connection is lost. So if you want to, you can write an event handler for the Disconnected event that displays "Disconnected" on a status bar, and then instructs the XceedFtp control to reconnect or perform other actions.
The XceedFtp control uses the standard COM mechanism for handling events. Expert developers that are familiar with implementing their own COM interfaces may want to use the library's custom interface advising capabilities if they prefer or require an alternate event handling mechanism.
The XceedFtp control allows you to specify which events are triggered by the library, so that you can disable events you don’t need. This eliminates the overhead incurred by triggering unused events and can improve the library’s performance. See the EventFilter property for details.
With Visual Basic, please see the topic about long integers.
With Visual FoxPro 5.0 and up, events will be triggered only if you set Application.AutoYield = .F.. Place this code in the section of your main program where you set up your environment. If you only have a single form in your application that uses the XceedFtp control, place Application.AutoYield = .F. in the form’s load method, and set it back to the default in the forms destroy method.
The following events are generated by the XceedFtp control. The "Applicable methods" section in each event's description topic indicates which methods trigger the event during their execution.
Code in event handlers for XceedFtp control events cannot recursively call XceedFtp control methods, except for ProcessCompleted event handlers. See the remarks section of the ProcessCompleted event for details.