topic Re: WrkBk reference in code No longer working with fresh install in SAS Programming

WrkBk reference in code No longer working with fresh install

texasmfp — Tue, 02 Feb 2021 00:34:42 GMT

I did a fresh install and, some code that worked perfectly before now now longer works. I recall that there may have been a hot fix related to ACCESS that may need to be re-applied. But that may be unrelated. Any ideas? Here is the code:

LIBNAME WrkBk EXCEL "&ROOT\&RESPONDENT._&SEGMENT._&STAGE._additional analysis.xlsx" SCAN_TEXT=NO;
PROC APPEND force BASE=WrkBk.raw
DATA=mfpresults;
RUN;
LIBNAME WrkBk CLEAR;

Here is the log:

SYMBOLGEN:  Macro variable ROOT resolves to E:\SAS Data\
SYMBOLGEN:  Macro variable RESPONDENT resolves to PT
SYMBOLGEN:  Macro variable SEGMENT resolves to AR1920
SYMBOLGEN:  Macro variable STAGE resolves to BASE1
MPRINT(G200_COST_SENSITIVITY):   LIBNAME WrkBk EXCEL "E:\SAS Data\PT_AR1920_BASE1_additional analysis.xlsx" SCAN_TEXT=NO;
ERROR: Connect: Class not registered
ERROR: Error in the LIBNAME statement.
ERROR: Libref WRKBK is not assigned.
MPRINT(G200_COST_SENSITIVITY):   PROC APPEND force BASE=WrkBk.raw DATA=mfpresults;
MPRINT(G200_COST_SENSITIVITY):   RUN;

Re: WrkBk reference in code No longer working with fresh install

Reeza — Tue, 02 Feb 2021 02:33:08 GMT

It seems like you may be missing the SAS/Access to PCFILES license portion. You can check what's installed with:

proc product_status;run;

and what's licensed with:

proc setinit;run;

Re: WrkBk reference in code No longer working with fresh install

texasmfp — Tue, 02 Feb 2021 03:18:32 GMT

Thanks Reeza. ACCESS was installed. Turns out the problem was that Office suite was installed as 32-bit. I uninstalled and re-installed in 64-bit. Problem solved.

https://support.sas.com/kb/43/933.html