About AlanC

AlanC · ‎06-24-2021

libname sqlite odbc complete="dsn=SQLite3 Datasource;Driver={SQLITE3 ODBC Driver};Database=e:\temp\IISHistoricalSample.db"; libname temp 'e:\temp' ; data sqlite.Sample; set temp.All_iis_new (obs=100); run;

AlanC · ‎06-14-2021

Make sure you are using the same dlls for EG. Check the versions. I can't debug it but I would suspect the dlls.

AlanC · ‎06-14-2021

An interface is a contract. If you implement an interface, you are expected to implement all of its parts. Here is a very basic example using pseudocode: interface IEGTask { public void Finalize() } class MyCustomTask : IEGTask <== Since MyCustomTask uses the IEGTask interface it must implement the Finalize method I don't know what your custom task does or how it works. if you open the class file where the error is happening, in Visual Studio, you can hover on the interface and say implement interface. Interface names always start with the letter I. You are missing one of them and, therefore, you are not following the contract. Interfaces say 'you agree to do x'. What happened is that the interfaces have been updated in EG and additional methods have been added. You are now out of interface contract compliance on your custom task.

AlanC · ‎06-11-2021

First of all, I think email is fine to use. Everyone likes their own means of communication and email works well. So does SMS and other means. Email/SMS show up while you are anywhere which is nice. That out of the way, when I send email I use a service. Our solution involves our own services but it is easy to use SMS or email services (ex. MailChimp using proc http. Look here: SAS Help Center: Syntax: PROC HTTP PROC HTTP Statement You will probably be using a POST command so follow that. Also, there are other services other than MailChimp. Pick whichever one works for you and do a REST call. REST makes everything easy w/o having to reinvent the world. There will also be REST calls for SMS.

AlanC · ‎05-19-2021

Most likely not. Perhaps another program installation. VBS will have a dll dependency. A reinstall probably put the dependency back in there but normally MS doesn't break the dependency on a reinstall. I would still suggest putting in more error checks into the script.

AlanC · ‎05-19-2021

The code seems to be failing on this check: If orderedList.Name = "MSR0002_CSV" Then orderedList.Run() End If I would check that you colleague has security rights to where the file is located. I would also make sure they have same version of SAS. Check in their installed apps that they also contain the correct Microsoft VC++ libraries (hunch on my part).. Make sure the libraries match yours. Finally, longer term, move away from VBS if possible. For now, put in additional error checks to look for mull values at key steps so you can isolate where the problem is occurring. My guess is that it is further up the food chain from where the code is reporting it.

AlanC · ‎04-29-2021

For text, use the '/' character to indicate new line. For example, the code below: put "Bonjour / Hi," / "Noter que le traitement CPE est maintenant completÃ©e / Take note that CPE process is now completed" // "Si vous dÃ©sirez plus d'information, s'il vous plaÃ®t contactez-nous / If you need more information, please contact us." //"Merci/Thanks," ;

AlanC · ‎04-27-2021

Well, it looks like you are reading the data in wrong from the get-go so not really an issue with blanks. It appears that your encoding is wrong somewhere or else you are reading in a source that is not text. As mentioned, what is the data source? It may be UTF-8/16 (or whatever).

AlanC · ‎04-27-2021

XLSX is not a good format to post results. Use text in the future so the hex values can be seen. Here is pseudo-code (aka I can't test it). PROC SQL; CREATE TABLE WORK.QUERY_FOR_FILTER AS SELECT STRIP(t1.Interest_Plan) AS IntPlan, COUNT(t1.Account_Nbr) AS Count FROM WORK.FILTER_FOR_FACT t1 GROUP BY IntPlan; QUIT;

AlanC · ‎04-27-2021

Use the STRIP function. If the raw data is such that you can pull it into a hex editor, try that. UltraEdit, Notepad++, and (my favorite for hex issues) 010 Editor can all show you the values. Look at encoding setup as well to make sure you are reading the values correctly.

AlanC · ‎04-21-2021

I replied worng so got a kickback. What I mentioned was git but sounds like that isn't it. Best thing I can suggest is check your AppData area. Your environment may be very different than mine. Find a unique string that corresponds to something you saved and search appdata for it including all sub-directories. I doubt it is lost and AppData is the best place to look. Make sure you search in all locations including hidden folders. I tried to replicate your scenario to no avail (didn't spend much time either). SAS would probably use git behind the scenes even is doing it local. Look for folders that are named '.git'.

AlanC · ‎04-21-2021

Check here: %APPDATA%\Roaming\SAS\EnterpriseGuide\7.1\mru.config

AlanC · ‎04-14-2021

I suspect DB or NAS issue, however... ...if you need to go low level to determine the slowdown, consider downloading sysinternals from Microsoft. Use the tools procmon (very low level access) and procexe to see the loaded dlls. Watch a video or read a blog ,especially on procmon, to know how to use it. It will tell you, in great detail, where performance is being hit. Procexe is like task manager on steroids. It will tell you what is consuming the system when EG is used. It may be an ancillary program. Procmon will capture EVERYTHING on your machine. Filter. filter, filter until you find clues. Ignore registry read/writes, for example (use buttons at top, right-click items to Exclude). If it is is a low level thing, you can rule it in/out.

AlanC · ‎04-02-2021

Make sure to minimize the columns desired. Your biggest impact will be to simply reduce the information obtained by only choosing what is needed. Columns are far, far more costly than rows. Use SELECT var names vs SELECT *. Agreed with what was said by pushing the query back to source but really, are all 500 columns used? This is not a SAS problem, per se. It is a design issue. Having 500 columns is a problem. SELECTs, WHEREs, GROUP BYs to overcome it. Again, reemphasizing, push the problem to the db.

AlanC · ‎04-02-2021

Compression can negatively impact a dataset and performance by a lot, in either direction. The characteristics of the data must be in line for compression to help. Without compression, all records in the SAS dataset are fixed width. If the columns are relatively tight (width matches content), compression will hurt. If the contents vary a lot, for example, lots of wasted address space (addr1, addr2, addr3), compression 'may' help. test it to find out. Lots of char columns with wasted space probably results in a positive impact. Lots of numerics probably hurts. Numerics in SAS are always doubles so compression does not help. I have seen dramatic changes by simply telling a client to turn off compression. Compression also has other negative impacts. Can it help? Yes. Should you default to using it all of the time? No.

Online Status	Offline
Date Last Visited	‎12-29-2025 09:47 AM

Re: Automatization of Code Extraction from SAS EG project

Re: How do I create a navigational table of contents of SAS code in SA...

Re: What is the quickest way to develop a simple SAS Enterprise Guide ...

Re: How to generate excel output with password protected

Re: How does Enterpise guide create the code when I use the tasks?

Re: How does Enterpise guide create the code when I use the tasks?

Re: How does Enterpise guide create the code when I use the tasks?

Re: SAS EG and Disk write

Re: SAS Stored Process - Pre process code

Re: Garbage collection in .egp file

Fun With SAS ODS Graphics: Veterans Day

Add SAS Packages Framework to the SAS Base/Viya

Re: multipart/form-data REST API POST in PROC HTTP failing

Re: Automatization of Code Extraction from SAS EG project

Re: How do I create a navigational table of contents of SAS code in SA...

Re: SAS EG and Disk write

Re: What is the quickest way to develop a simple SAS Enterprise Guide ...

Re: Add SAS Packages Framework to the SAS Base/Viya

Re: Export SAS table to sqlite3

Re: The add-in does not contain the correct interface signature

Re: The add-in does not contain the correct interface signature

Re: Email from EG when bandwidth exceeded

Re: SAS Enterprise Guide 8.2 VBS Error

Re: SAS Enterprise Guide 8.2 VBS Error

Re: how to work with accented text

Re: Extrange results using trim and compress functions

Re: Extrange results using trim and compress functions

Re: Extrange results using trim and compress functions

Re: Transfer Program History to New SAS Enterprise Guide Installation

Re: Transfer Program History to New SAS Enterprise Guide Installation

Re: SAS EG 8.3 Performace Problem

Re: Performance for tables with so many columns via ODBC.

Re: Performance for tables with so many columns via ODBC.

SAS Global Forum 2019