Mysql 4.0? Are you sure? Not 4.1? Since there was an error with 4.1/5.0 + datetime fields, which exacty produces this kind of errors...
Try if it's really the DateTime (select id, organisation, etc from table) and tell me which release of fpc you're using. It would be the best if you use the newest one... On Wed, 2006-05-03 at 08:32 -0700, Jon Foster wrote: > Using the A TMySQL40Connection to access MySQL I get the following error: > > ":2" is an invalid integer > > While using a TSQLQuery running the following SQL: > > select * from tests > > Can anyone shed some light on this. I've tried setting "ParseSQL" to > false, which would defeat my purpose. Even with that I keep getting this > error. Some times the ":2" will be a ":3". There are three other > TSQLQuery objects in use that don't have problems. They all have similar > queries they just access different tables. > > I'm wondering if this doesn't have something to do with data types. Here > is the structure of the table: > > Field Type Null Key Default Extra > > id int(11) PRI auto_increment > > organization int(11) MUL 0 > > name char(32) > > target char(128) > > test char(16) > > next_run datetime MUL 0000-00-00 00:00:00 > > frequency int(11) 0 > > last_run datetime 0000-00-00 00:00:00 > > result char(4) > > > All of the tables in question have very few records. They probably will > never exceed 30 records per table. > > THX - Jon > -- Met vriendelijke groeten, Joost van der Sluis CNOC Informatiesystemen en Netwerken http://www.cnoc.nl _________________________________________________________________ To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe" as the Subject archives at http://www.lazarus.freepascal.org/mailarchives
