newbie Crystal Reports question

[Brad Allison]

Okay, I am totally green to Crystal Reports, however I do have the general
concept of how the reports work.

I have a dataset being filled by a parametized data adapter, however when I
run the call to open the Crystal Report viewer, I have a dialog box appear
that wants me to logon to the database server. How can I stop this dialog
box from appearing?

This is VB .Net, using Access as a backend over a network. Thanks for any
information and I apologize in advance if this is the wrong forum to post
to.

Brad

 

[Guest]

CR address this BUG on their site.
http://support.businessobjects.com/search/default.asp?ref=default.asp_selectlisttc
http://support.businessobjects.com/library/kbase/articles/c2012606.asp
http://support.businessobjects.com/library/kbase/articles/c2013545.asp

One work-around is to set a unique username and no password, passing the login name will work, its the password thats the problem.

Also, try making an ODBC connection to the server where you have your DB. Then no UNS\PSW is needed.

Below are some CR examples for Web and Windows application.
http://www.wizkil-webs.net/NET/DotNET_Code_Samples.htm#_Toc76872011

Hope this is of some help.
B

 

[Brad Allison]

Brian,

I deleted all current OleDb data adapters, connects and datasets associated
with the report and re-created the same using ODBC. When running the
report, I still get the database login screen so could the problem lay
somewhere else?

Brad

CR address this BUG on their site.
http://support.businessobjects.com/search/default.asp?ref=default.asp_selectlisttc
http://support.businessobjects.com/library/kbase/articles/c2012606.asp
http://support.businessobjects.com/library/kbase/articles/c2013545.asp

One work-around is to set a unique username and no password, passing the

login name will work, its the password thats the problem.

 

[Brad Allison]

Thanks for the link. I will try this and let you know. Why does this have
to be so complicated. It should be black and white. "Report, here is the
dataset filled with the data I want you to show; now show it!"

It could be. We had this as a major problem. how we got around it was we

created a SQL account that didn't need a PSW just a USN. Then on the users
PC we made an ODBC System DSN connection for said DB with USN no PSW.