Hey Mike,

>I'm doing great

Awesome! Glad to hear it.

>yes, after executing loCommand.Execute for (Update)
>I have looked true the loCommand.*
>under locommand.ActiveConnection.Errors.Count I have 1
>but I can't find any other info that would help me with problem filed.
>the table has about 130 fields.
>where else can I look for the filed name that is causing the problem?

You didn't mention what the error attributes were:

?loCommand.ActiveConnection.Errors.Item(1).Description
?loCommand.ActiveConnection.Errors.Item(1).Number
?loCommand.ActiveConnection.Errors.Item(1).Source
?loCommand.ActiveConnection.Errors.Item(1).SQLState
** it might be zero based, I always forget

So are you using Parameter objects? Or are you building your UPDATE statement from scratch? Or is this a SP call?

Is it possible you are passing a NULL value to a field that does not allow NULLs?

If you are using Parameters objects, could one of your field values be transposed from a numeric field to a character value...or visa versa?

You may have to go through and eliminate fields until the problem goes away...then that is your troubled field.