>I don't have a specific answer, maybe someone else has come across this.
>
>But in general, if you put your data retrieve/update commands inside a try-catch block, you can trap the exception and see what the generated error message is.

This is what I have. But, this is too generic and does not provide any information on what the error is all about.