RE: Connecting the iseries thru crystal in a VB app

["Angela Wawrzaszek" <awawrzaszek@xxxxxxxxxxxxxxx>]

It is our VB developer that is asking me for help.  She is new to the
as/400 and cannot figure out why it is / is not connecting and is
reaching out to me.  I checked the ODBC setups,  crystal database
reference within the report etc.  and couldn't find anything that I knew
of that was wrong,  that's when I turned to you.   I will try searching
the crystal web site and see if it has anymore to offer.  

Thanks!

-----Original Message-----
From: Vern Hamberg [mailto:vhamberg@xxxxxxxxxxxxxxxxxxxxxxxxx] 
Sent: Wednesday, June 30, 2004 9:20 AM
To: Midrange Systems Technical Discussion
Subject: RE: Connecting the iseries thru crystal in a VB app

When a VB app is packaged, it is possible (automatic, almost) to include

all the files it needs in order to run properly when installed
elsewhere. 
This should include the Crystal DLLs. Find out who is working on this
app 
and ask them for the references and components that are defined in the
VB 
project. Or ask them to run the packaging and deployment wizard. This
way 
you won't be just guessing.

Hope this is a start. This is not a 400 problem, actually. You might
also 
go to Crystal's web site and check their knowledge base, which is quite 
extensive.

At the end of the day, this is the responsibility of your VB developer,
IMO.

HTH
Vern

At 06:56 AM 6/30/2004, you wrote:
>Yes,  it is an in house application.  The application only bombs out if
>the user does not have crystal installed on their pc and they choose
the
>report part of the application first.  If they have crystal and using
>the same application choose the report first it is fine.
>
>Viewing the ODBC connection on the crystal report everything looks
fine.
>That's why I think it must be some sort of .dll or something else that
>needs to be on the pc without crystal to allow it to connect to the
>iseries without an actual connection first.  It seems like the crystal
>report will not connect on its own,  even though the odbc is fine.
>
>-----Original Message-----
>From: Adam Lang [mailto:aalang@xxxxxxxxxxxxxxxxxxxx]
>Sent: Tuesday, June 29, 2004 3:45 PM
>To: Midrange Systems Technical Discussion
>Subject: Re: Connecting the iseries thru crystal in a VB app
>
>It almost sounds like it builds connection at a certain point in the
app
>and
>by going to the report first, the connection isn't being built,
>therefore it
>bombs out.
>
>Is this a program that is written in house?
>
>----- Original Message -----
>From: "Angela Wawrzaszek" <awawrzaszek@xxxxxxxxxxxxxxx>
>To: <midrange-L@xxxxxxxxxxxx>
>Sent: Tuesday, June 29, 2004 3:19 PM
>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!


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.