Charlotte Foust
cfoust at infostatsystems.com
Tue May 31 17:30:25 CDT 2005
Actually, it dawned on me that the records were being imported into a temp table first and when I checked, the fields, which were checked to allow nulls in the ultimate destination table, were missing that property in the temp table. Fortunately, I wasn't the one who created them. ;-> Charlotte Foust -----Original Message----- From: Susan Harkins [mailto:ssharkins at bellsouth.net] Sent: Tuesday, May 31, 2005 3:16 PM To: dba-sqlserver at databaseadvisors.com Subject: RE: [dba-SQLServer] Import Errors Charlotte, would it be possible to create a mock table with the same settings and link to it to see if you get the same error? If not, you could just import the data into the new table. I've seen phantom characters cause this kind of mischief in Access, and you'll never find the culprit. Susan H. I'm beating my head against some import errors that don't make much sense. I've got an Access FE with linked SQL Server tables and one table is giving me "Null value in an auto-number field" errors for two fields, neither of which is an autonumber. One of them is actually a text field declared as varchar in SQL Server. The other is declared as a smallint, but is set to allow nulls and is not required. Neither is set as an identity field. HELP! _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com