Problem viewing Crystal Report written against FoxPro ole db

[jstangel]

I have a report created with an FoxPro OLE DB datasource. When I run the report in developer on my local machine, I do not get prompted for a login and the report runs successfully. When I save the report out to InfoView and try to view it, I get prompted for a login and anything I enter is rejected. This report should not be prompting for a login at all. I have other reports written against other types of datasources that don't require a login and I have no issues. Anyone have any idea how to get it to not prompt for a login?

 

[jstangel]

So not quite sure what I did, but I tried this report again in BO Enterprise and it appears to be working now when I schedule it.

To be specific, I decided to try it again. I went back to my original reports written against the ODBC connection I had initially created. I reset the datasource location on the reports to the OLE DB connection (which I set using the full server path, eg \\servername\shared\dbfolder). I saved a fresh copy to Enterprise. When I try to run it on demand, I am still getting a prompt for a log in that I can't get past, but if I schedule the report with no log in, it is now running successfully. Previously it was failing saying I had invalid login credentials when I tried to schedule it.

However, any suggestions on how to fix the issue when trying to run it on demand would be appreciated.