OK folks,
This has been exhaustively tested, fixes have been applied, it's been kicked upstairs to the master developers...
1. Is anyone still seeing this issue?
2. If so, would you be willing to let one of our techs log into your computer remotely to see if they can reproduce?
Nobody here has been able to reproduce this error, and failing that, we would need to let this one go.
At this point the consensus seems to be that *maybe* there was a functional change when FT was upgraded last spring, and a small number of FTers in an edge case were affected by it -- BUT the software is actually working as designed.