I'm trying to run a simple SQL update via ODBC and I'm getting the following error:

Microsoft OLE DB Provider for ODBC Drivers (0x80004005)

[DataDirect][ODBC SequeLink driver][ODBC Socket][DataDirect][ODBC FileMaker driver][FileMaker] (-1)

What does this mean?

The SQL it's using at the moment is:

UPDATE Auctions Set Notes = Notes + ' 10/10/2006 - 2:02:01 PM - Drew Angell: Successfully filed NPB.', Auction_DisputeID = '342343', Auction_Status = 'Loser', Non_Paying_Bidder = 'Yes', Date_NPB_Filed = '10/10/2006' WHERE Auction_ID = '221267'

I've also tried removing the single quotes from around the number fields:

UPDATE Auctions Set Notes = Notes + ' 10/10/2006 - 2:02:01 PM - Drew Angell: Successfully filed NPB.', Auction_DisputeID = 342343, Auction_Status = 'Loser', Non_Paying_Bidder = 'Yes', Date_NPB_Filed = '10/10/2006' WHERE Auction_ID = 221267

with the same result.

Any information on what's going on here would be greatly appreciated. Thanks!

Ok I just took everything and added 1 field at a time to the update until I found the problem. It's the updating of the date field.

I don't see why that's not working, though. The field in FileMaker has a datatype of Date and I'm trying to put 10/10/2006 in there. Why is this drawing an error?

Hmmm...ok, it seems to not like the date being submitted as a text value with the single quotes around it. I remove those and then the update does work, however, it goes into the SQL like 10/10/2006. So the SQL actually runs 10 divided by 10 divided by 2006 and puts a crazy decimal in the Date field. Which seems weird to me since the field has a data type of date...why does even accept that value?

Ok, well sorry for the bogus thread. I just realized SQL has it's own DATE() function and that seems to solve the problem.