Karen-
I'm not sure this applies to your situation, but when we have seen this, it
was due to work being assigned as fractional amounts. For example, a 5 hour
task over 3 days reflects as 1.666666 hours per day. Actuals were entered by
the resource as 1.66 hours per day and PWA said the task was complete. MS
Project didn't. There ended up being a tiny amount of remaining work
leftover. It wasn't visible in PWA since PWA only reflects 2 decimal places.
Same with MS Project. By looking at the Assignments table in the database,
we saw that there was .0066 hours remaining.
Now, we have run into training issues whereas some resources enter their
actuals exactly as assigned. Even if the resource really worked 2 hours, he
entered 1.66. Had he entered 2 hours, the assignment would have been
reflected as complete both in PWA and MS Project.
The only way we could "fix" this was to go into the Task Usage view for the
project, find the assignment, and enter 0 for remaining work. Then we
Republished and Overwrote work entered by the resource. This basically
"forced" the assignment to show as complete". Again, this may not be the
situation you are in, but I thought I would offer it.
Good luck!
Christina