More fun with Crystal reports . . . I had a new report fully configured and signed off on and was all set to publish to our report system when I made a wonderful little discovery: when running the report, the viewer would fail with the (seemingly infamous) error message stating that the "report you requested requires further information" and then presenting a dialog box for the server name, database, user and password with some of the values filled in. Even by filling those values in, however, the report would still not render, firing log in failure exceptions. After much searching and subsequent banging of my head against my desk, I finally came across what seems to have been the issue. I had been using the SQL Native Client for the OLE DB (ADO) provider. It appears that this provider doesn't work correctly with the Crystal architecture. Instead, for Crystal to be able to log in correctly, the data provider needed to be mapped to the "Microsoft OLE DB Provider for SQL Server." After making that one simple change, everything worked like a charm. Shame I couldn't find that documented anywhere . . .