Would you consider re-doing this so that it comes back in a variable? That would make it much easier to automatically work with. Also, it could then be consistent with the COM object -- how does the COM object handle errors now?
My experience, but I'm not willing to bet the farm on this like I sometimes am, is that specifying an invalid directory does not create the directory if it doesn't exist. Maybe it doesn't work with UNC paths, or if the path is invalid (e.g. a drive that doesn't exist), instead of throwing an error it continues (and creates nothing). Again, I'm not willing to bet the farm, but I know I've had problems in that area. Anyway, I re-submit my request for a return variable rather than a throwing a failure. Personally, I'd like to see something like the # of messages queued, or the # of .mail files created, but for now just a reason for failure would be good. Tac ----- Original Message ----- From: "Howie Hamlin" <[EMAIL PROTECTED]> To: "inFusion Support List" <[EMAIL PROTECTED]> Sent: Tuesday, January 21, 2003 4:58 PM Subject: Re: [iMS] blank emails > The tag throws a ColdFusion exception on an error. > > Regards, > > Howie > > ----- Original Message ----- > From: "Tac" <[EMAIL PROTECTED]> > To: "inFusion Support List" <[EMAIL PROTECTED]> > Sent: Tuesday, January 21, 2003 4:30 PM > Subject: Re: [iMS] blank emails > > > > What is the name of the variable to check if an error has occurred? What > > are the possible values? > > > >
