To me this looks like either a server encoding issue or an issue with the myODBC driver. We still use the myODBC 3.51.12 as we have found a number of issues with the newer drivers when used on Windows server 2003 SP2, with the IIS app ...
read more »
Be the first to post a Comment!