Yes it will raise an error which can be caught using any of the vb error trapping methods. But it may not tell you what is wrong just that there is some sort of automation error. This is fine in most situation as you are aware of the context in which the error was generated & can therefore anticipate what the error is likley to have been caused by; but not always.