Hi, for me the problem turned to be that the vendor didn't have a ver 3 ODBC driver (which J odbc scripts are set up for). There's a beta version of it available, but I haven't got around to giving it another try yet.
Thanks go to Bill Lam for restoring my sanity through helping me interpret column definitions. I wouldn't have known that the date type id was a version 1 id. If you really need data in another type, you might consider casting the variable server side to a J friendly one. You could do this in the SELECT statement, and then re-alias the column. For BLOBS, depending upon what's actually in it, you could deconstruct it server side (that's probably more trouble than it's worth though... go for the former suggestion). I'm not up-to-speed with the MySQL SQL dialect... maybe someone else could help with the particulars on that. cheers, -Steven ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
