Prev: PROC FCMP VARARGS Weirdness
Next: Excel Read-In Oddity
From: Chris T on 15 Oct 2009 17:12
I got an e-mail response from someone about this. Apparently I'm not
the only having problems...

I asked SAS via the tech support why they don't just provide the
necessary DLLs to connect to MySQL instead of relying on the end-user
to install their own. Haven't heard back on that. I'm hoping it's a
legal thing...
From: Chris T on 19 Oct 2009 13:16
options set=SASMYL MYWIN417;

That right there is what has caused all my frustrations.

I've been reading this instruction guide:
http://support.sas.com/documentation/installcenter/92/sasinstall/9.2/win/wx6/config.pdf

It says to include it, but SAS tech support just told me not to. And
not including it works.

Oi. What a week. But glad to be up and running. :D
From: bizwald on 3 Nov 2009 12:23
On Oct 19, 10:16 am, Chris T <chris.tin...(a)gmail.com> wrote:
> options set=SASMYL MYWIN417;
>
> That right there is what has caused all my frustrations.
>
> I've been reading this instruction guide:http://support.sas.com/documentation/installcenter/92/sasinstall/9.2/...
>
> It says to include it, but SAS tech support just told me not to.  And
> not including it works.
>
> Oi.  What a week.  But glad to be up and running.  :D

Hey guys. I just found this on support.sas.com:
http://support.sas.com/kb/37/512.html
Now I have to work on making the options statement version specific
since I have both 9.1.3 and 9.2.0 on my system.

Hope this helps.
First  |  Prev  | 
Pages: 1 2
Prev: PROC FCMP VARARGS Weirdness
Next: Excel Read-In Oddity