Thanks Naomi... I tried searching the threads but evidently didn't use the right combination of key words.
For anyone that finds this thread, it seems that switching drivers has fixed this problem.
I switched from
driver={SQL Server Native Client 10.0}
to
driver={SQL Server}
Brandon Harker
Sebae Data Solutions