Date:         Tue, 5 Jan 2010 12:39:21 -0600
Reply-To:     "Data _null_;" <iebupdte@GMAIL.COM>
Sender:       "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From:         "Data _null_;" <iebupdte@GMAIL.COM>
Subject:      Re: Libname Function and Connection Strings
Comments: To: zrab123@comcast.net
In-Reply-To:  <1579242554.6272841262716106104.JavaMail.root@sz0080a.emeryville.ca.mail.comcast.net>
Content-Type: text/plain; charset=ISO-8859-1

I THINK init_string would go in the LIBNAME function's forth parameter, OPTIONS.

options
names one or more options honored by the specified engine, delimited
with blanks.

If you can't get it to work you may be able to use CALL EXECUTE to
execute the LIBNAME statement.

On 1/5/10, Ken Barz <zrab123@comcast.net> wrote:
> We have a generalized macro that creates libname assignments based on values passed in a metadata dataset using the libname function. Naturally, now we have a new data management system that breaks that. So, if I have a libname that looks like so:
>
> libname datain oledb init_string="Provider=VFPOLEDB.1;Data Source=&inpath.\_system.DBC";
>
> is there some syntax to get the libname function to set using the init_string stuff? The simplified data step we're using is something like:
>
> data _null_;
> set meta.tsc_current_header;
> if type='libname' and include='Yes' then do;
> if parameter = 'DATAIN' then do;
> libn = libname(parameter, resolve(value) , 'oledb');
> end;
> else do;
> libn = libname(parameter, resolve(value));
> end;
> end;
> run;
>
> where parameter is the libname and value (for all other libname assignments) is the path.
> Thanks,
> Ken
>