>Have you ever determined the problem here? I'm getting the same error since moving to Server 2003, and it's getting REAL annoying!

Frankly, no, we didn't. The customer probably ran the import from one of the W2k boxes for the remainder of the season, and the next season I wasn't available to patch the app. I passed all the source to them, and I think the guy there just redid pretty much everything on SQL server and ASP. Don't know what else was he using, but the guy looked really smart. So the stuff isn't running anymore, and I have no clue to what happened.