We have several reports which (currently) corss-reference some information from SQL Server with some information in an Access database. These reports work fine in Crystal Reports, but, once they've been exported to Enterprise, they cannot seem to log in to the Access database, though they appear to be properly directed to it. The Access database doesn't (or shouldn't, anyway) require any credentials to pull data out of it, so why does Crystal Enterprise insist on logging in? Is this masking another error?