We have an application (Desktop) that has been using SSCE for quite some
time (Since version 2.1, but we upgraded to 3.5/SP1). Up until yeserday,
I had never encountered this particular problem. I have to say I'm
completely baffled by what this error tells me. I have specified a
constraint name for the default, but it appears it is attempting to
generate a new one and use that instead, except that the name it is
generating is apparently already in use.
Here is the error:
Error executing SQL: alter table ReserveTrades add column
ManuallyCreated bit not null constraint DF_ReserveTrades_ManuallyCreated
default 1 ---> Constraint already exists. [
DF__ReserveTrades__000000000000099C ]
I would provide the stack trace, but it does not provide any insight.
Has anyone encountered this type of error before? Is it a known bug? Any
info at all would be helpful. Thank you.
Chris
ErikEJ - 23 Nov 2008 18:53 GMT
Could this be related:
http://blogs.msdn.com/sqlservercompact/archive/2008/04/03/dropping-defaults.aspx

Signature
Erik Ejlskov Jensen, Mobile App Dev MCTS
Check out my SQL Compact blog at
http://erikej.blogspot.com
> We have an application (Desktop) that has been using SSCE for quite some
> time (Since version 2.1, but we upgraded to 3.5/SP1). Up until yeserday, I
[quoted text clipped - 13 lines]
>
> Chris