Hi,



We have just installed 1.7.0.6 and are conducting testing. We have just had the 'Data Collision' dialogue appear and this is curious in that:



1) It has neve appeared before while conduting this set of test.

2) The dialogue box itself is empty, i.e. is doesn't show what fields caused the collision.



Anyone seen this in their 1.7.0.6 testing?



Cheers, Peter

Hi,



I should have mentioned all our BO's use:



OptimisticRowVersion



and we leave the version number column to be automatically maintained by SF.



Cheers, Peter

Just to give you a level of comfort here, let me point out that this has not changed and we too use OptimisticRowVersion for all tables (and BOs) and I have not seen anything like this.  Also, we have been running the 1.7.0.6 version of the business objects in our medical application for 4 months, and so I am very confident in the build.  So we may want to investigate some other things in your environment.  I don't doubt that you saw the collision dialog, but there could be data being moved into the BO outside of a standard query or something along those lines that is causing this to happen.  If you can get it in a reproducable state I will be more than willing to take a look at it.

Hi Trent,



Thanks for the prompt repsonse. Certainly this part of our app is far from standard processing. I guess the issue for us it hasn't happened before 1.6.0.7. and the fact the dialogue box was empty. I will get back if we can't resolve the issue ourselves.



Cheers, Peter

Does sound a bit curious, but I would really need a sample or something to work off of to try to reproduce.  Let me know if you come up with something.  Thanks!

Hi Trent,



Yes, we did sus it out in the end.



This particular form does do nonstandard things and, prior to 1.6.0.7 is closed cleanly. After 1.6.0.7. under certain circumstances it showed a 'Do you want to save the change' dialogue. We presumed it was SF improved object disposal that caused this happen and didn't worry about. To fix the problem we added a few IsDiry Then Bo.Save on the form close. This kinda worked except occasionally we would get the data collision dialogue that I asked about. We replaced the IsDirty code with BO.Clear and all is fine.



Cheers, Peter

Great, glad you got it figured out!