R
ragtopcaddy via AccessMonster.com
The following query works fine in 2003, but gives me data type mismatch
errors in 2007. There are 241 records that have 0s when I run the select
portion of the query in 07, and there are 241 records that can't be appended
due to conversion failure (I believe). Coincidence? I think not!!!
INSERT INTO tblNBV ( Storid, NBV, Remaining, DoR )
SELECT DISTINCT Store, NBV, [Remaining Allowance], #9/9/2008 4:41:44 PM#
FROM xlNBV
WHERE Store In ( SELECT [Store #] FROM tblStoreMaster )
This append query is part of a download process that reads data from a named
range in an Excel worksheet, and appends it to a table in Access. The field
with the 241 0's is [Remaining Allowance], and it actually displays as 241 "-
" characters. Access 2003 had no problem interpreting this field and
appending all 985 records to the table. When I try to run the same procedure
in Access 2007, the .execute statement fails.
Unfortunately, this is happening on my client's Access2007 machine at work,
and I am at home, so I can't duplicate the error here as I don't have
Access2007 here. On my client's machine, I don't currently have web access,
so I have to try to explain from memory.
errors in 2007. There are 241 records that have 0s when I run the select
portion of the query in 07, and there are 241 records that can't be appended
due to conversion failure (I believe). Coincidence? I think not!!!
INSERT INTO tblNBV ( Storid, NBV, Remaining, DoR )
SELECT DISTINCT Store, NBV, [Remaining Allowance], #9/9/2008 4:41:44 PM#
FROM xlNBV
WHERE Store In ( SELECT [Store #] FROM tblStoreMaster )
This append query is part of a download process that reads data from a named
range in an Excel worksheet, and appends it to a table in Access. The field
with the 241 0's is [Remaining Allowance], and it actually displays as 241 "-
" characters. Access 2003 had no problem interpreting this field and
appending all 985 records to the table. When I try to run the same procedure
in Access 2007, the .execute statement fails.
Unfortunately, this is happening on my client's Access2007 machine at work,
and I am at home, so I can't duplicate the error here as I don't have
Access2007 here. On my client's machine, I don't currently have web access,
so I have to try to explain from memory.