Overview (Dundas Upload Control 2.0)

Dundas

Overview (Dundas Upload Control 2.0)

Copyright © Dundas Software Ltd. 2000, All Rights Reserved.

Overview | Properties | Methods


The Dundas Upload Control is an MTS component which allows you to accept, save and manipulate files uploaded via a web browser. It is used in Active Server Pages (ASP) which are hosted with either Microsoft's IIS (Windows NT or Windows 2000) or Microsoft's PWS (Windows 9X).

Dundas Upload Control 2.0 Features:

  • Web farm ready.

  • MTS support (object pooling).

  • ADO support via safe-array-of-bytes variants. Allows you to persist uploaded files as BLOBs.

  • Handles uploading of multiple files and form data.

  • Upload form data either all at once or incrementally. Incremental retrieval of data allows the developer to access some of the form data prior to the upload as well as skip files to be uploaded.

  • Lets you specify a maximum allowable limit for uploaded data, a maximum number of files to be uploaded as well as a maximum allowable file size.

  • Implement a progress bar via the ProgressBar component and the Dundas StateServer.

  • Save uploaded files either to disk or to memory.

  • Performs numerous file and directory operations.

  • Impersonate user accounts other than the IUSR (or default) account, thereby allowing you to perform operations for which the default account does not have permissions.

  • COM registration.

  • MacBinary support (for Macintosh client machines).

  • Uploaded files ACL, owner and attribute manipulation.

  • Disable or set the default values of certain features via the registry.

  • Handles file downloading.

  • Optionally save uploaded files with unique filenames.

To create an instance of the Upload control use the CreateObject method with a ProgID of either "Dundas.Upload" or "Dundas.Upload.2".

To utilize named constants in your code use a server-side include for the DSUpload.inc file, which defines the constants for you.

Most methods of the control will throw an exception if an error occurs. Trap for the success/failure of the various operations by using an On Error Resume Next statement and then examine the Err object after a method call.

You should find the following topics especially useful:

See Also: Progress Bar Component Overview | State Server Component Overview