Using LLBLGEN 2.5 with dotnet2

Have a webservices that saves an entity to database. I have a field called DateModified that i set on the client and save to the database through the webservice.

When i return the entity to the client and compare DateModified that is returned with what i sent..it is different by 1 millisecond?

Why?

I am comparing the sent DateModified to returned DateModified to ensure entity has been saved.

Must be something in your code We can't tell as we don't have the code.

Anyway I'd have set the DateModified on the server, if it's the current date.

Could it be a rounding difference due to difference datetime resolutions in dot.net vs the database server's datetime implementation?

i have heard of this problem before with datetime values for concurrency. it also exists if a given row is updated multiple times within a millisecond. The prefered solution is to use the timestamp column type which is stored as a binary. if it increments by 1 then it was updated. if it doesn't increment, it was not updated. finally, if it is incremented by more than one it was updated mulitple times since the last time saved.

The date is sent using XML date encoding, though I think it can be that the differences are in millisecond ranges because for example sqlserver uses a lower precision than .NET for time values.