----- Original Message ----- From: "Pugh, Eric" <[EMAIL PROTECTED]> > The reason I set my ID method to none was because I couldn't get Torque to > work correctly with my preexisting tables. Our database is MS SQL Server > 2000, and all our tables use an identity column for the primary key. When I > had autoincrement set, I seem to recall that it would try and insert my > primary key value, with a null, or something like that.. (I don't quite > recal). When I switched to none, it worked. I understand though that > "none" is deprecated, and at somepoint, "autoincrement" will do what I want. > > I will run another test with autoincrement to verify the behavoir I was > getting. BTW, I am using TDK 2.1 > > Eric
I think I glossed over the fact that you said MSSQL as well. It looks like the MSSQL howto could use more information on this point. I don't know if torque autoincrement is implemented for MSSQL so perhaps idbroker is the better choice for now. Scott -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
