I FOUND A SOLUTION!!!! And it only took me 18 hours...
Thanks for the help mwvisa1 and although your suggestions did not provide a direct solution, you did put time into this so I'll definitely award you some points.
The solution was in the connection string. Apparently, on certain servers running SQL 2008 this driver:
Driver={SQL Server Native Client 10.0} is treating the time data type differently than
Driver={SQL Server}
Although I don't have an explanation of why this was happening (I am not a database guru) I do know that changing the default driver helps resolve this issue.
So bottom line that the Native Client 10.0 interprets certain data types differently. And changing the time precision to time(0) from the default time(7) or whatever you may have it set it to, will help better fit older applications/code. Hopefully there aren't many dinosaurs like me using Classic ASP.