My concern with this is for someone coming behind you and using your code and understanding it...the additional documentation required seems like a lot more text than a few parameters to the intnx function. ... View more

Have you tried highlighting each node in the process and copying? I'm pretty sure that used to work ... View more

Certain objects can't be copied like a user defined link, therefore if included in your selection you will not be able to copy hence the grey'd out copy. Not sure if better in 4.3 ... View more

so i guess the answer is no. Thanks for the conformation! ... View more

You can't. Eguide tasks rely heavily on the physical attributes of their inputs. When absent they will not work. I find this one of the (many) differences with Data Integration Studio which is fundamentally based upon metadata. If this is an issue for you consider saving your intermediate results permanently, e.g. by using the EGTASK or SASUSER library. You can control this by setting Options. Be careful not to fill up your storage however. Giving meaningful names to the intermediate tables (instead of QUERY_FOR_...) helps. A lot. Regards, Jan. ... View more

cool, thanks ... View more

I'm not sure this is the proper place for these kind of suggestions. Try this form under SASWare Ballot: http://support.sas.com/contact/software_comments.html /Linus ... View more

This is a bug in EG 4.2, but has been fixed in EG 4.3. It only occurs when opening the data after an attempted open on the data has already failed at least once during that session (one scenario: someone else had the data open in update mode the first time you tried to open). If you encounter the issue, you can workaround it by saving, closing, then reopening your project or by removing the data element from your project/process flow, then readding and reopening the data. ... View more

got it. thx ... View more