What we narrowed the cause down to seems to be a broken link in that user's account in the registry to a particlar table in the database.

In other words, one process that resolved the issue was to delete the "Documents and Settings" folder for that user than recreate it.

What is happinging is that we use a local tempoary database for each user. That tempoary database is stored on the workstation's local drive. Each user on a terminal server has their own temp database. That temp database is used to store the results of queries for the purpose of having the Crystal report templates bound to via ODBC. We do not bind the crystal templates directly to the main database. This way I can have several copies of the database: development, test, production, snapshots, etc. Regardless of which database the user is pointing to during a print query, the results of the query is stored in that users' private local database.

For some unknown reason, the crystal template at runtime for that user only fails on page 3 of the template. I origionally thought it had something to do with a registry problem with a crystal DLL. Now I suspect that each of the database tables paths are also stored in the registry per user id. And the problem may be as simple as a broken registry link for one table, thus the crystal template could not find that table.

Any thoughts?