Article ID	2027
Article Title	ERROR: "Logon Failed" on Crystal Reports when using INT files
Article URL	http://www.dataaccess.com/kbasepublic/kbprint.asp?ArticleID=2027
KBase Category	Crystal Reports
Date Created	07/22/2004
Last Edit Date	07/22/2004

Article Text
PROBLEM:
I want to use INT files from Crystal Reports to give my reports the same flexibility as my (Visual) DataFlex programs. However, as soon as I select an INT file I first get a dialog that let me confirm the INT file location and then I get a "Logon Failed" error.

ANSWER:
The minimum required version of the Connectivity kit that supports INT files is 9.0.0.45. Next to that you need to have a Crystal Professional, Developer or Advanced Developer license.

As written in the users guide for the Crystal Reports Connectivity Kit in the chapter on troubleshooting, the error "Logon failed" means that something failed when opening the table. Crystal Reports reports this as "logon failed".

There are, however, some issues you need to take care of:
1. Crystal must be able to find all necessary components. This means all DLL, EXE, CFG, DFR and INT files (don't forget about the Data itself!). Since not all of these files will be in the BIN directory for Crystal the best way is to add the BIN directory of your (Visual) DataFlex license in the Windows PATH. The files that need to be found are: DfDaemon.exe, APIDLL.DLL, <CKNAME>.DLL (e.g. ODBC_DRV.DLL), <CKNAME>.DFR, <CKNAME>.CFG

2. Also check if there is a DLL with the name of your Connectivity Kit plus the suffix 110570 in the same spot as your CK DLL. In the case of ODBC_DRV.DLL there should be a ODBC_DRV110570.DLL. If the file is missing check if the process has rights to create one. The file will be automatically created by the API but when this fails, Crystal reports the same Logon Failed problem. You can make a copy of the CK DLL with this prefix manually if the process cannot create the DLL. Make sure the copied DLL does have the exact same version as the original CK DLL. You can check the version of a DLL via the Windows floating menu | Properties when you right-click on the DLL file.


REMARK:
The use of INT files makes it easier to design reports for multiple backend databases and, thus, enables you to offer your software to customers with a varierity of backend databases.

If you have only one backend database you should consider using drivers offered with Crystal Reports since the use of INT files will probably have a negative impact on the process speed of your reports compared to native, direct access by Crystal itself.


Contributed By:
Vincent Oorsprong
Company: Data Access Worldwide
email: vincent.oorsprong@dataaccess.eu
Web Site: http://www.dataaccess.eu

Links Related to this Article
DAW Knowledge Base article 1968: HOWTO: Avoid Problems with Crystal Reports 9 running from VDF

Email this Article
Email this Article to a Colleague
Send Feedback on this Article to Data Access Worldwide
Copyright ©2024 Data Access Corporation. All rights reserved.

The information provided in the Data Access Technical Knowledge Base is provided "as is" without warranty of any kind. Data Access Corporation disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. In no event shall Data Access Corporation or its suppliers be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business profits or special damages, even if Data Access Corporation or its suppliers have been advised of the possibility of such damages. Some states do not allow the exclusion or limitation of liability for consequential or incidental damages so the foregoing limitation may not apply.