Chris Jordan
Tue, 30 Oct 2007 11:51:22 -0800
Hi folks, I've got a weird one that I hope someone can help me with. I just got a call from a client saying that they were getting the error (I'm paraphrasing here): "There was a problem instantiating the COM object. AutomationException:null"
The problem happened just in the production code and not in my development version (both on the same machine). I then began comparing the relevant files between dev and production. The files were identical. I then closed the files, tried to reproduce the error again and now it's gone. The client isn't pulling my leg here, I saw the error occur too. I don't like errors like this that are here one second and gone the next with no real explanation. Since my code didn't change, I'm assuming that this is either some CF problem which maybe I should use some try/catch logic to avoid it breaking -- or -- there's something up with the .dll that makes up the COM object that I'm using. Any thoughts or suggestions? -- other than it's probably a bad idea to have my production and development code on the same machine... ;o) -Chris -- http://cjordan.us
_______________________________________________ Reply to DFWCFUG: List@list.dfwcfug.org Subscribe/Unsubscribe: http://lists1.safesecureweb.com/mailman/listinfo/list List Archives: http://www.mail-archive.com/list%40list.dfwcfug.org/ http://www.mail-archive.com/list%40dfwcfug.org/ DFWCFUG Sponsors: www.instantspot.com/ www.teksystems.com/