> We encountered this, and circumvented this by defining our fields
> as DOUBLE(x,y) to ensure that a standard precision set is used.
Very nice workaround!
(Well, as long as you don't need the extra precision.)
If you've done any testing as to which x,y parameters work and which
don't, I'd appreciate seeing the results of your findings. You could
add them to bug 5225 too...
> The workarounds were (a) use double or decimal type
Using DOUBLE doesn't seem to be a viable workaround..
> set LastWins to true in the commandbuilder.
Disabling optimistic concurrency would do the trick if you're coding
manually, but won't work if you're dragging controls onto your GUI
in the IDE and have no control over the CommandBuilder.