Myles
Nothing really - just wanted to conform to a standard since it was there
There is a procedure in ADODB
CreateUDLFile(const FileName, ProviderName, DataSourceName: WideString);
but for some reason it takes the ProviderName and DataSourceName and joins
them (which I thought is the connection string)
and stores it as a UDL but it fails
Regards
Neven
----- Original Message -----
From: Myles Penlington <[EMAIL PROTECTED]>
To: Multiple recipients of list delphi <[EMAIL PROTECTED]>
Sent: Tuesday, 27 June 2000 09:40
Subject: RE: [DUG]: Connection String vs UDL
> Whats wrong with just using a connection string Neven?
> Or for that matter saving the connection string to a file??
>
> > -----Original Message-----
> > From: Neven MacEwan [SMTP:[EMAIL PROTECTED]]
> > Sent: Tuesday, June 27, 2000 10:39 AM
> > To: Multiple recipients of list delphi
> > Subject: [DUG]: Connection String vs UDL
> >
> > Hi Guys
> >
> > Has anyone tried prgrammatically creating UDL files for an ADOConnection
> >
> > From the M$ documentation it pretty much says that a UDL is just a
> > connection string
> > So I tried saving an ADOConnection to a File but it don't work
> >
> > TIA
> >
> > Regards Neven
> > N.K. MacEwan B.E. E&E
> > [EMAIL PROTECTED]
> >
>
> --------------------------------------------------------------------------
> > -
> > New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED]
> > Website: http://www.delphi.org.nz
> --------------------------------------------------------------------------
-
> New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED]
> Website: http://www.delphi.org.nz
>
---------------------------------------------------------------------------
New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED]
Website: http://www.delphi.org.nz
