Thanks Jeff for opening up a wonderful opportunity. PPM doesn't seem to bring t files. So I've never heard of them. Now I'm scurrying around looking for them in other modules. What a great resource! Regards Clinton ----- Original Message ----- From: "Jeff Urlwin" <[EMAIL PROTECTED]> To: "'Clinton'" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Friday, June 27, 2003 3:17 AM Subject: RE: Time Field & M$ Access
> > Hi List > I'm tring to insert a timestamp > Using DBI 1.14, ActiveState 5.6, Access 2000 > SQL =INSERT INTO tblCar (date_now,time_now) VALUES > (#06/23/2003#,#16:13#) > Results in > DBD::ODBC::st execute failed: [Microsoft][ODBC Microsoft > Access Driver]COUNT field incorrect (SQL-07001)(DBD: > st_execute/SQLExecute err=-1) at > C:\project\parse\callback2.pl line 100. [Microsoft][ODBC > Microsoft Access Driver]COUNT field incorrect > (SQL-07001)(DBD: st_execute/SQLExecute err=-1) at > C:\project\parse\callback2.pl line 100. > > However it works when running directly in Access. (If I > remove the time_now it works thru the DBI) Can't figure out > the error code. Help appreciated. Regards Clinton > Please see examples in the DBD::ODBC distribution. The correct ODBC format for the date/time is used in a variety of the t/*.t files. The problem here is that the MS Access front-end does *not* always do the same thing as the ODBC back-end. The front-end changes things and interacts "more directly" with the DB engine. You need to stick with ODBC / SQL standards and you'll be ok. Regards, Jeff
