Crystal Report Viewer. Logon Failed Details: [Database Vendor Code:18456}

I am running Sage Accpac version 5.5 on a 64 Bit windows 2008 Virtual server.
The database is SQL 2005 and reside on a different physical server. I created various customized reports using Crystal Reports XI. These reports were created by linking to views that was created in the SQL database. I link to the database with a ODBC (RDO) connection for all the reports. I can run all the reports from the Crystal Reports designer. However when I want to run them from the Accpac desktop I get the following error when running some of them

Logon Failed Details: [Database Vendor Code:18456]

Strangely enough the reports are all linked to the database in exactly the same way (ODBC) the only difference is that use different views.

Advice on this issue will be much appreciated.
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Are the views in the main report or a subreport?  The latter is probably necessary, Accpac has issues with views in the main report.
Alternatively, you can create a DSN for reporting which uses a trusted connection.  Ensure that the users have read access to the database and you should be good to go.
CR XI doesn't support 64-bit Windows.

Do you have the 32-bit ODBC drivers loaded?

The 7 Worst Nightmares of a Sysadmin

Fear not! To defend your business’ IT systems we’re going to shine a light on the seven most sinister terrors that haunt sysadmins. That way you can be sure there’s nothing in your stack waiting to go bump in the night.

This relates to security within the report.  You must select "use trusted connection" within the report when creating the connection, and the connection needs to match the Accpac database connection configuration.
@scott -

Accpac doesn't use trusted connections, it uses SQL authentication.  Its Crystal wrapper replaces database login info, but only for tables in its data dictionary, hence the problem with views that it doesn't know about.
malcolmaddisonAuthor Commented:
Thanks guys
The issue was that although I had the views in both the main and sub-reports the visible views in the reports referred to other SQL views that was not directly in the reports.

Thanks for all the replies. This issue is now resolved.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
thanks, Jay, you're right, of course :)
malcolmaddisonAuthor Commented:
Issue Resolved
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Crystal Reports

From novice to tech pro — start learning today.