While emulating cursors, OpenX doesn't saves result sets in it's memory buffer. It fetches row by row from SQL server's memory buffers instead. This technique is highly optimized, and aimed to scroll read-only records in a forward-only manner. Such method saves memory on machine where OpenX's instance was created.

One of important OpenX features is protected connection. OpenX won't crash or raise ASP error if network or SQL server problem occurs. Also, it may happen if somebody kills OpenX process on SQL server. ErrorCode will return "-9999999" in that case. Executing Disconnect() and after that Connect(), will return OpenX to normal state.

Calling isEmpty after Execute() has the side effect of moving the cursor to the first row of the result set (if any).
We recommend using "do ... while ( MoveNext() )" in that case.

This feature of OpenX greatly simplifies HTML Form processing and File uploading procedures. Only few strings of code needed to validate posted HTML Form and save its data into the database. If this form includes one or more <INPUT TYPE=FILE> tags, the files will be received by OpenX and stored onto server's hard drive or saved right into the database. Only one submit button is required for a form containing any combination of HTML form elements plus the upload file elements.
OpenX provides all the functionalty of standard File uploading components: it will show the type of file, its extention and size, aggregate amount of bytes transferred during given upload session, and will allow you controlling the 'overwrite' switch and the size of uploads.
OpenX will validate posted HTML forms, ensure that all mandatory fields are filled properly, and even check the validity of email addresses and credit card numbers.