Skip to main content

We are trying to send email by SMTP and came across a code by David Sands called CDODemo.

CDODemo worked flawlessly. 

Problem with CDODemo is in the exception handling.

there is nothing after the statement:  invoke    ws-cdomess   "send"

that is to show a successful execution.

We need to use an error number or successful code to test.  Eventually, this is to enable a web cgi program to display the appropriate message.

We looked inside CDO2000.cpy and did not get any elaboration on the "send" function.

 


#CDOSysonerrorexceptionNetExpress5.1

We are trying to send email by SMTP and came across a code by David Sands called CDODemo.

CDODemo worked flawlessly. 

Problem with CDODemo is in the exception handling.

there is nothing after the statement:  invoke    ws-cdomess   "send"

that is to show a successful execution.

We need to use an error number or successful code to test.  Eventually, this is to enable a web cgi program to display the appropriate message.

We looked inside CDO2000.cpy and did not get any elaboration on the "send" function.

 


#CDOSysonerrorexceptionNetExpress5.1

This demo uses the COM interface to CDO so any errors that may occur are trapped as OLE exceptions and will be displayed within the exception handler entry point.

If no exception is raised then the exception handler will not be called and you can assume that the send was successful.

The exception handler code (if you have the same version that I do here) is:

callback section.
entry "onOleException" using by reference lnkErrorObject        
                            by reference lnkErrorNumber        
                            by reference lnkErrorText.          
   display "OLE Exception:-"                                    
   display "The COBOL exception number was: " lnkErrorNumber
   display "The exception occured on:"                          
   invoke lnkErrorObject "display"                              
   invoke EntryCallback "new" using z"DispError"                
                                 returning wsIterator          
   invoke lnkErrorText "do" using wsIterator                    
   display "Terminating.."                                      
   stop run                                                    
   exit program.                                                
entry "DispError" using lnkElement.                              
    display "    " with no advancing   *> Indent Slightly      
    invoke lnkElement "display"                                
    display " "                                                
    goback     


We are trying to send email by SMTP and came across a code by David Sands called CDODemo.

CDODemo worked flawlessly. 

Problem with CDODemo is in the exception handling.

there is nothing after the statement:  invoke    ws-cdomess   "send"

that is to show a successful execution.

We need to use an error number or successful code to test.  Eventually, this is to enable a web cgi program to display the appropriate message.

We looked inside CDO2000.cpy and did not get any elaboration on the "send" function.

 


#CDOSysonerrorexceptionNetExpress5.1

Thanks for the explanation Chris.

Yes. We looked at the callback section.  It is the same as what you have there.

In this case, we can just follow the "send" with housekeeping codes assuming a successful operation.

Thanks again.


We are trying to send email by SMTP and came across a code by David Sands called CDODemo.

CDODemo worked flawlessly. 

Problem with CDODemo is in the exception handling.

there is nothing after the statement:  invoke    ws-cdomess   "send"

that is to show a successful execution.

We need to use an error number or successful code to test.  Eventually, this is to enable a web cgi program to display the appropriate message.

We looked inside CDO2000.cpy and did not get any elaboration on the "send" function.

 


#CDOSysonerrorexceptionNetExpress5.1
Hi Chris,

Concerning the CDO code by David Sands... it's now that I'm using it in NetExpress v3.1. An error "OLE Exception:-" of 00065537 is being sent back to the program. What is this mean?

I've installed the new updated "ExchangeCdo.MSI" from Microsoft website and it is still not working.

We are trying to send email by SMTP and came across a code by David Sands called CDODemo.

CDODemo worked flawlessly. 

Problem with CDODemo is in the exception handling.

there is nothing after the statement:  invoke    ws-cdomess   "send"

that is to show a successful execution.

We need to use an error number or successful code to test.  Eventually, this is to enable a web cgi program to display the appropriate message.

We looked inside CDO2000.cpy and did not get any elaboration on the "send" function.

 


#CDOSysonerrorexceptionNetExpress5.1
Hi Chris,

Concerning the CDO code by David Sands... it's now that I'm using it in NetExpress v3.1. An error "OLE Exception:-" of 00065537 is being sent back to the program. What is this mean?

I've installed the new updated "ExchangeCdo.MSI" from Microsoft website and it is still not working.

We are trying to send email by SMTP and came across a code by David Sands called CDODemo.

CDODemo worked flawlessly. 

Problem with CDODemo is in the exception handling.

there is nothing after the statement:  invoke    ws-cdomess   "send"

that is to show a successful execution.

We need to use an error number or successful code to test.  Eventually, this is to enable a web cgi program to display the appropriate message.

We looked inside CDO2000.cpy and did not get any elaboration on the "send" function.

 


#CDOSysonerrorexceptionNetExpress5.1
Hi Chris,

Concerning the CDO code by David Sands... it's now that I'm using it in NetExpress v3.1. An error "OLE Exception:-" of 00065537 is being sent back to the program. What is this mean?

I've installed the new updated "ExchangeCdo.MSI" from Microsoft website and it is still not working.

We are trying to send email by SMTP and came across a code by David Sands called CDODemo.

CDODemo worked flawlessly. 

Problem with CDODemo is in the exception handling.

there is nothing after the statement:  invoke    ws-cdomess   "send"

that is to show a successful execution.

We need to use an error number or successful code to test.  Eventually, this is to enable a web cgi program to display the appropriate message.

We looked inside CDO2000.cpy and did not get any elaboration on the "send" function.

 


#CDOSysonerrorexceptionNetExpress5.1
The 65537 error simply means that a COM error occurred There should be a secondary error code that is the actual COM error that occurred.

Something like:
Exception 65537 not trapped by the class oleexceptionmanager.

Description: "Server defined OLE exception"

(80020009): Exception occurred.

Net Express 3.1 is an extremely old unsupported product version. It may not be compatible with newer software and operating systems. Please keep that in mind.