I am using ms sql server 2005 and this problem had bothered me for long time. At last I found it was caused by a few unique indices of some tables (You can find them by searching with "unique="true"" in files entitymodel.xml). After I changed them into "unique=false", demo data works fine. Can anybody explain why this problem doesn't exist with other database servers, and why we need to set unique=true at some indices while most others are unique=false?
Weixue Zhang -- View this message in context: http://www.nabble.com/problem-Running-with-MS-SQL-tp24895969p24992345.html Sent from the OFBiz - User mailing list archive at Nabble.com.
