Ben,
Hanging is not a behavior that would point to a specific consistent problem. Either there is something unique about the report, or something is unique about the config of the server that allows it to run. You have to identify the differences, and that means double checking some things.
Check to see that "Verify Database on every print" is not set differently. Unless the database structure changes frequently, I wouldn't use this setting.
Do the other reports use the same database, tables, join types?
Do they have similar parameters?
Do the workstations have the correct version of CRPE?
Do they all have permissions to all files and workspace?
In other words, what are the uniquenesses of this report or environment. That might point you in the right direction.
[sig]<p>Ken Hamady<br><a href=mailto:ken@kenhamady.com>ken@kenhamady.com</a><br><a href=
Reports Taining by Ken Hamady</a><br>[/sig]