RE: Connecting the iseries thru crystal in a VB app

Is it possible that when you run crystal reports as a stand alone app it
uses a different DSN (Data Source Name) than the VB app? For example our
VB apps use Client Access to connect to our iSeries using OLEDB to pull
data from the iSeries and dump everything into Excel, but we have some
separate Excel spreadsheets that import data with a different Client
Access ODBC DSN. It might be helpful to look at the Control
Panel>Administrative tools>Data Sources(ODBC) to see if there is an ODBC
DSN that was created for Crystal Reports. If there is that might be the
data source that crystal reports uses when it is run as a stand alone
app. You might be able to look at the properties of the DSN to see if
there is a user id hard coded there. It might also be helpful if you can
look at the VB app and see how it is connecting to the iSeries.
 
-----Original Message-----
From: Angela Wawrzaszek [mailto:awawrzaszek@xxxxxxxxxxxxxxx] 
Sent: Tuesday, June 29, 2004 2:20 PM
To: midrange-L@xxxxxxxxxxxx
Subject: Connecting the iseries thru crystal in a VB app

     We have a VB app that connects to our iseries and displays various
forms of data,   there is also a crystal report that can be selected to
display.   If the user goes to the other parts of the app first the
connection for the iseries is established and the crystal report runs no
problem.   If the user first selects the crystal report the program
bombs out saying the user id is invalid for the connection and shows our
system IP address.   If we look at the ODBC connection the crystal
report uses it uses the system name NOT the IP address.   This process
works fine if the user has crystal installed.     The app is packaged up
with just about every .dll that we can find for it.

 

Can anyone help or point us in the correct location?

 

Thanks!