First, thank you for your reply. I use 1 or more background SAS session before I want to run two or more job asychronously, for example, a ETL job and Forecast job at the same time. I have found the reason: the DoWork method is in the background session, and the RunWorkerCompleted in the foreground session, so if I create obSAS2, get OleDbconnection2, run sas codes only in the same sesion, that's will be OK. I have tested it in my EG Add-in for several days, there is no problem, at last until today. Although SAS open a door to enhance EG by development of Add-in,  there are still too few materials about the development, so another question. SAS.Tasks.Toolkit.SasServer obServer; try {    obServer = new SAS.Tasks.Toolkit.SasServer( consumer.AssignedServer); }...... How to get SAS workspace from the obServer, I know I can get SAS workspace from "consumer", but if connection between server and EG is broken, I must re-connect manually by hands, now I try to do it by codes. I find the method SAS.Tasks.Toolkit.SasServer.GetWorkspaceIdentifier() Remarks This method will force a connection to the SAS server, if the connection does not yet exist. The connection might cause a slight delay. It might also force a prompt for user ID and password, depending upon the configuration of the server and its metadata. ... View more

Thank you, your post is very helpful. but there is another question. You kwow, the purpose I create obSAS2 is to perform background processing and the user need not to face frozen UI and wait for a long time before the result coming out. See the following codes, expecially the line with comments, sasDbAdap.Fill(srcTable); I don't why there is a NullReferenceException thrown, do you have experience of using obSAS with BackgroundWorker? At last, If try to close obSAS2, is my way OK or not?     obOK.RemoveObject(obSAS2);     obSAS2.Close();   /*----------------------------------------------------------------------------------------------------------------------*/ private void bgWorker_DoWork(object sender, DoWorkEventArgs e) {     bgSuccess = true;     if (obSAS2 == null || obSAS2.UniqueIdentifier.Length == 0) {         obSAS2 = obSAS.GetNewWorkspace();         SasServerCount++;         obOK.AddObject(SasServerCount, SasServerCount+":SASBK", obSAS2);     /*Stored Process Execution*/         sasDbConn2 = new OleDbConnection();         sasDbConn2.ConnectionString = "provider=sas.iomprovider.9.2; SAS Workspace ID=" + obSAS2.UniqueIdentifier;         sasDbConn2.Open();     } } void obSASLang2_StepError() {     bgSuccess = false; } private void bgWorker_RunWorkerCompleted(object sender, RunWorkerCompletedEventArgs e) {     OleDbDataAdapter sasDbAdap = new OleDbDataAdapter("select * from sashelp.class", sasDbConn);     try {         sasDbAdap.Fill(srcTable);  /*Error: NullReferenceException*/     } catch (Exception ex) {         bgSuccess = false;     }     if (bgSuccess)       this.grd.DataSource = srcTable;           /*Close obSAS2*/     obOK.RemoveObject(obSAS2);     obSAS2.Close();   } ... View more

Thank for your reply first. I'll keep tracking. By the way, I don't think it's a better way that: Ok,that's not perfect enough, so try another way not perfect enough, everything is not perfect enough. Hehe! ... View more

Thank you for your suggestion. but I think why would we talk about the COMPRESS option, the final reason is that we want to compress dataset and reduce storage space. so if VARCHAR is supported by dataset, the COMPRESS option perhaps is meaningless. ... View more

SAS is keeping the balance between coding facility and storage, but time is to bring a revolution on this, or SAS would cost more than 5 times storage space than other databases. I want to know when will varchar type be supported by SAS data set, instead of char type? ... View more

Easier with SAS/Access to PC-File module. ------------------------------------------------------------------------------------- data tmp; set sashelp.class; label name='new name' sex='new sex' age='new age' height='new height' weight='new weight'; run; libname xls "c:\123.xls"; data xls.'new sheet'n(dblabel=yes); set tmp; run; libname xls clear; ... View more

Ods tagsets.tableEditor can be used directly in stored process, I have tested it successfully. ... View more

I modified a few codes of "tableeditor.tpl" downloaded from SAS SUPPORT, then ran proc template; define tagset Tagsets.Tableeditor/store=work.templat; ............... then got the log: NOTE: TAGSET 'Tagsets.Tableeditor' has been saved to: WORK.TEMPLAT then I ran: proc template; path work.templat; list tagsets; run; and got the log: 2688 proc template; 2689 path work.templat; 2690 list tagsets; ERROR: Unable to restore 'Base.Template.Stats' from template store! 2691 run; ... View more