On Sat, 13 Sep 2003, Jeff Urlwin wrote: > I'd *highly* recommend installing the latest MDAC (2.7?) from Microsoft on > both the server and the client (security reasons for the server and correct > working queries on the client. If that still shows the problem, let me > know. I don't see it here. If you do see it, send me a small example that > reproduces it.
We now have MDAC 2.8 on both ends (client & server) but we still see the problem. Unfortunately, I can't give you a simple recipe because I'm accessing the database entirely through stored procedures which I have no control over (welcome to my hell). It basically seems to happen whenever a stored procedure returns non-character data, as we've seen it for both integer & datetime types. Another weird thing is that if the stored procedure declares a return type to be BIGINT I get something back like "201,123,456,789.00\0x00", so it is somehow being _formatted_ somewhere. I'm guessing that this isn't something DBD::ODBC itself is doing, but no one can figure out where it could be happening. -dave /*======================= House Absolute Consulting www.houseabsolute.com =======================*/
