🚀 go-pugleaf

It 's not a good idea to allow NULLs on a column that should be part of a
unique index,
because in that case with sqlserver NULL = NULL and therefor there can be
only one.

Check this :
create table T_test1 (col1 int null, col2 varchar(100) NULL)
go
create unique index Ux_T_test1 on T_test1 (col1)
go

insert into T_Test1 (col1, col2) values (1,'test1')
go
insert into T_Test1 (col1, col2) values (2,'test2')
go
insert into T_Test1 (col1, col2) values (3,'test3')
go
-- this one is ok
insert into T_Test1 (col2) values ('Test firts col1-null')
go
-- this one will fail
insert into T_Test1 (col2) values ('Test second col2-null')
go
insert into T_Test1 (col1, col2) values (4,'test4')
go

select * from T_test1
go

drop table T_test1
go


Jobi
"^-^" <mortalnightmare@hotmail.com> wrote in message
news:b7ito9$5kt$1@ctb-nnrp2.saix.net...
> Hi there...
>
> I have a table called dc_weighbridge_MAIN that that has to have an unique
id
> called [ticket] but "ticket" also has to allow null values... so i set the
> ticket field to allow null fields, but to check for duplicate entries I
> created a view called "check_duplicates" wich a form will be based on as
> soon as this function is working....  in the view I added all the records
> but made "ticket" an unique index...
>
> Now when I try to delete or add any records in my table (not even using
the
> view) I get the error: DELETE failed because the following SET options
have
> incorrect settings: 'ARITHABORT'
>
> What's wrong?  What I want to achieve is: When my capturer inserts a
record
> that has an "ticket" no there may be no duplicates, and the form should
warn
> you of this when you try to add the record to the sql server, if the
> capturer adds a record that doesn't have a "Ticket" then it will use
another
> form that will be based on another view similar to this one that will be
> based on another "Unique ID" called [Heat_nr]
>
> Plesae help, Thanks alot in advance :)
>
> ^-^
>
>