Thanks for the quick response, Craig. That code is in several methods and classes of a Crystal wrapper object and would be hard to post here effectively.

I did some further experimenting and discovered the following: The original reports that both those in question were developed from had been created in a single subdirectory with both the .rpt files and the fox 2X tables co-resident. Later the two were split out into separate subfolders, i.e., CRYSTAL\REPORTS and CRYSTAL\DATA. Apparently the problem stemmed from the weird (stupid!) Crystal habit of keeping hard-coded-path copies of literally every constituent component. I noticed this when I attempted to "Refresh" the database information and had to add the \DATA portion of the path. Once I had done this, the version of the report that had formerly been working in the runtime environment now also raised the "Logon failed" error. In all cases the wrapper class loops through the object model of the report and replaces the "Data File" property of the .Tables.ConnectionProperties collection with the full path of the appropriate table in the runtime environment, so I still don't understand why this should have been an issue at all, since all that transpired before the viewer was ever instantiated.

Ultimately I had to rebuild both reports by completely removing the data source at design time and then replacing it with the same source--now correctly pathed in the development environment. When those new template .rpt files are now used at runtime, with the same wrapper class data rejiggering, everthing works as advertised.

Why it previously functioned properly on the development machine but not runtime is still a bit of a mystery to me.

>What does the code look like that instantiates the Crystal components and handles database locations, etc?

Ray Roper