Madox,
Interesting. I've _never_ seen the server return "" for those variables,
and it's not ever supposed to return "" for those variables, which is why
there's no defensive code around that. I suppose the driver could "punt"
when it runs into this situation, but I smell a memory overwrite condition
somwehere in the server.
Is this issue reproducible?
-Mark
Hello Mark thank you for the reply. No unfortunately we have not been able to reproduce this. The DB is being upgraded from 4 to 5 so we may not see this issue again. I have not seen this issue reported anywhere else but it may not be a bad idea anyway to put some "defense" around the code that retrieves those variables?
Regards,
Maydox