I agree with Steven adding any filter to the primary index
is kinda going against its definistion
Arnon
> Adding the index is definitely not the solution, nonethelesst an index on
> Deleted() is always a good idea.
>
>
> >>>What's the table update error, Lar?
> >>>
> >>>>I have...
> >>>>2 simple related tables
> >>>>Using views on both to update.
> >>>>Referential integrity on the parent table has deletions cascading to
> the child
> >>>>SQL send updates to both with delete and insert
> >>>>Primary keys on both tables = keyfield for not dele()
> >>>>
> >>>>The child table updates fine.
> >>>>
> >>>>Any parent table update results in error. The only thing that I
have
> been able to guess is that the parent table's delete may be trying to
> cascade to the the child.
> >>>>
> >>>>Is there a way that I can have the parent use the delete and insert
> update? I want to be able to see the previous entries.
> >>>>
> >>>>TIA
> >>Index uniqueness violated. I checked all fields and the values are
in
> fact unique. Other info..the two tables are related thru another field
> called orderid...just thought that I might need another index on that one
> "for not dele()"...stay tuned...//:^)
> >That was it. I needed the "for not dele()" clause on my relation index.
> Now the problem is that since I have cascading deletes, the delete and
> insert update is deleting my child records, but not adding them back in.
> Can I temporarily "turn off" the cascading delete?
>
Previous
Reply
View the map of this thread
View the map of this thread starting from this message only
View all messages of this thread
View all messages of this thread starting from this message only