Any clues to what the database is doing in the SQL log file?

Regards

eljeffo,

As "1/1/1900..." is the default date when a date column can not be null, could it be that the process you are seeing this on just has not executed a...

OUCH...plagued by the "to many hours" syndrome. That fixed it.

Thanks for the help!