I'm sure its working as designed but...

I have a table which is going to show the addresses of sites for companies. Its keyed on company code (integer) and site id (integer) and I was going to keep a sequential number for site within company. I realised I was wasting my time and have altered the site id to autoinc using DBSys.

Because of the fact that its a composite key there's no problem but I now have a column of autoincs virtually all with a value of 1.

It doesn't matter because when I transfer the data for real its starting as an autoinc and everything will be hunky dory I was just surprised to see all the ones and thought I'd report it.



Roy Lambert

Roy,

<< I have a table which is going to show the addresses of sites for
companies. Its keyed on company code (integer) and site id (integer) and I
was going to keep a sequential number for site within company. I realised I
was wasting my time and have altered the site id to autoinc using DBSys.

Because of the fact that its a composite key there's no problem but I now
have a column of autoincs virtually all with a value of 1.

It doesn't matter because when I transfer the data for real its starting as
an autoinc and everything will be hunky dory I was just surprised to see all
the ones and thought I'd report it. >>

DBISAM doesn't change the value of existing columns during an ALTER TABLE,
regardless of whether they are now an autoinc column or not.  We would be in
big trouble if it did.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim


Fair enough - I thought that would be the answer - just seeing 1 1 1 1 1 1 in an autoinc looked really strange.

Roy Lambert

Roy,

<< Fair enough - I thought that would be the answer - just seeing 1 1 1 1 1
1 in an autoinc looked really strange. >>

Well, at least it isn't:    6  6  6    

--
Tim Young
Elevate Software
www.elevatesoft.com