Thanks brendthess, that took care of the milliseconds for SQL Server. I tried to adapt the code to handle microseconds for DB2, but have begun to run into an accuracy problem. One of my testing timestamps(db2) looks like:

1997-07-28-14.55.36.816200

But VB is returning it as:

1997-07-28-14.55.36.816000

Close, but that whole horseshoe and handgrenade thing comes into play. Those damn picky users and their data accuracy .

Thanks again, if anyone has any additional insight, I'm all ears.