[AccessD] Upsize errors

Another:

Server Error 15135: Object is invalid. Extended properties are not permitted
on 'dbo.tblClaim.tblClaim_FK11', or the object does not exist.

EXEC sp_addextendedproperty N'MS_ConstraintText', N'You cannot add, change,
or delete this record because of the relationship restriction between the
tables ''tmmPolicyProductType'' and ''tblClaim''.', N'user', N'dbo',
N'table', N'tblClaim', N'constraint', N'tblClaim_FK11' 


John W. Colby
www.ColbyConsulting.com 

Contribute your unused CPU cycles to a good cause:
http://folding.stanford.edu/
-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Stuart McLachlan
Sent: Thursday, December 22, 2005 12:02 AM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Upsize errors

On 21 Dec 2005 at 23:54, John Colby wrote:

> I am getting a TON of these kinds of errors.
> 
> CREATE UNIQUE INDEX ER_Reason ON tlkpEventReason(ER_Reason)
> 
> Server Error 1505: CREATE UNIQUE INDEX terminated because a duplicate 
> key was found for index ID 3. Most significant primary key is 
> '<NULL>'. Server Error 3621: The statement has been terminated.
> 
> I am confused as to how Access could have a unique index that SQL 
> Server is finding a duplicate key for.  I have not gone looking yet.
> 

Was the index in Access on a field that had 'Required" set to "No". or was
the index designed with "Ignore Nulls" set to "Yes"?
In either case, you could have Null records in the index and that appears to
be what is causing the problem based on the above message.

 
-- 
Stuart


-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com