Creating an ODBC DSN or using ADO with Client Access
Lee Parker
but I have been unable to successfully create an ODBC DSN for Client Access
(as a part of installation) and I have also been unable to get the ADO
provider IBMDA400 to work...
My current work-a-round for people beta testing the application is to have
them manually create the ODBC DSN (and I always seem to have to walk them
through it - I guess my documentation isn't what it should be)...
I am also not using the SystemObjects drivers because of installation
difficulties (I have never been able to get the silent install to work, plus
you have to install part of the BDE and the installation gets very
complicated).
My executable is 500K, and I'd prefer to let it self install the ODBC DSN or
use ADO if I can get a working example on how to form the connection string
(the property editor does not work for that driver for some reason, and I
have tried it on Win95 & Win2K Server).
Any help would be greatly appreciated!
Thanks,
Lee
Brion L. Webster
> I need to deploy an application that connects to a database on an AS/400,
> but I have been unable to successfully create an ODBC DSN for Client Access
> (as a part of installation) and I have also been unable to get the ADO
> provider IBMDA400 to work...
>
with Client Access Objects from:
http://members.home.net/sgoldsmith/client.htm
If you choose to use them, all you need to have is CAE installed on the user's
system. It's a lot like DOA for Oracle. They can be a little finicky when
testing new SQL statements, sometimes you get a great error message, sometimes
just an AV, but I really like the ease of deployment. Our in-house distribution
of CAE doesn't include the db2 driver, so we couldn't use the BDE's SQLLinks
driver. Client Access Objects has eliminated all the install / setup hassle.
-Brion
A few notes for working with Client Access Objects:
You need to supply all of the helper cao components, in addition to the
caoQuery:
caoSecurity1: TcaoSecurity; // may be the only optional component
caoErrorMessage1: TcaoErrorMessage;
caoDatabaseConnection1: TcaoDatabaseConnection;
caoQuery1: TcaoQuery;
caoDatabaseSQL1: TcaoDatabaseSQL;
caoDatabaseDataFormat1: TcaoDatabaseDataFormat;
caoDatabaseParmMarkerFormat1: TcaoDatabaseParmMarkerFormat;
caoDatabaseSQLCA1: TcaoDatabaseSQLCA;
You must change two properties on caoDatabaseSQL:
defaultBlockCount to 32 or 64 and
defaultScrollableCursor to caodbCursorScrollable
You must set the relevant dependancy properties (like errorMessage) in all cao
components.
You must leave all active properties as False when saving & compiling your
project. It is probably better to manually activate the dependant components
prior to activating a query in design-time.
On the main form's close event, close all cao components that have an active
property:
caoQuery1.Close;
caoQuery1.Active := False;
caoDatabaseSQL1.Active := False;
caoDatabaseConnection1.Active := False;
Serge Charbit
As the CEO of SystemObjects I can't accept your problems using our product.
We can help you to understand how to use the silent mode and plus there is
now a new deployment license named Delphi/400 Automatic Deployment license,
which is done to deploy and UPDATE automatically all your applications i.e
Delphi/400, the BDE and your applications. And without any need to "visit"
each of your PC's users.
Please take contact with us at sa...@systemobjects.com and let us know where
you are, so we can call you back.
Thanks
Serge
"Lee Parker" <l...@i4get.com> wrote in message
news:8rfa27$3r...@bornews.borland.com...
> I need to deploy an application that connects to a database on an AS/400,
> but I have been unable to successfully create an ODBC DSN for Client
Access
> (as a part of installation) and I have also been unable to get the ADO
> provider IBMDA400 to work...
>
Steve Swett
Until I get more time to try to resolve that one, I've been working with
ODBC and DSNs.
My solution was to create a small Delphi program called "Extract DSNs" which
you run once on a PC that is already successfully setup. This displays all
the system DSNs on that machine and lets you select the ones you want to
distribute to clients. It puts the DSN info in a file somewhere on your
network. Then I have written another program called "Install DSNs" which
can be run at each client PC. The process run on the client does not show
any pop-up screens or dialogs, so if you can find a way for your
installation program to "run" this, then you'll be able to get the DSNs
installed automatically. If you can't figure out how to do it
automatically, at least all you have to do is have the end user click a
single shortcut to get the DSNs installed.
If you'd like me to send you the programs and the source code, I'd be happy
to (Delphi 5).
Lee Parker wrote in message <8rfa27$3r...@bornews.borland.com>...
Topp_rolmc
Lee Parker wrote:
> I need to deploy an application that connects to a database on an AS/400,
> but I have been unable to successfully create an ODBC DSN for Client Access
> (as a part of installation) and I have also been unable to get the ADO
> provider IBMDA400 to work...
>
> My current work-a-round for people beta testing the application is to have
> them manually create the ODBC DSN (and I always seem to have to walk them
> through it - I guess my documentation isn't what it should be)...
>
> I am also not using the SystemObjects drivers because of installation
> difficulties (I have never been able to get the silent install to work, plus
> you have to install part of the BDE and the installation gets very
> complicated).
>
> My executable is 500K, and I'd prefer to let it self install the ODBC DSN or
> use ADO if I can get a working example on how to form the connection string
> (the property editor does not work for that driver for some reason, and I
> have tried it on Win95 & Win2K Server).
>
> Any help would be greatly appreciated!
>
> Thanks,
> Lee
--
Topp
HSB99 BS35
'97 FLHRP Drifter