Charlotte Foust
cfoust at infostatsystems.com
Thu Jul 31 10:25:25 CDT 2008
We have to be careful in our .Net code to always test for 0 or <> 0 because we run against both Access and SQL Server. Trying to test for True crashes on one or the other. Charlotte Foust -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Susan Harkins Sent: Wednesday, July 30, 2008 4:48 PM To: Access Developers discussion and problem solving Subject: Re: [AccessD] upsizing oooooooooooooo.... I like that. :) Susan H. > Possiby because Access uses -1 for True and you can't represent that > with a bit? > > What value does SSMA store insert a True record (1 or -1)? > > > On 30 Jul 2008 at 18:45, Susan Harkins wrote: > >> SSMA converts Access Yes/No fields to tinyint, instead of bit -- does >> anyone have an explanation for that? >> >> My guess is it's because SQL Server's bit didn't support NULL's until >> 7.0, but it seems like the wizard would keep up with something like >> that. I really can't recall if Access' Yes/No always supported NULLs >> or not. >> >> Susan H. >> >> -- >> AccessD mailing list >> AccessD at databaseadvisors.com >> http://databaseadvisors.com/mailman/listinfo/accessd >> Website: http://www.databaseadvisors.com > > > -- > AccessD mailing list > AccessD at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/accessd > Website: http://www.databaseadvisors.com -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com