Blaming the victims is probably a too strong critic but the fact that such interpreter error was never fixed and this post has no SAS people helping does reflect how SAS deals with its problems. Many people continue to use SAS only because the company they work has legacy SAS datasets, think about how many new grad actually learnt SAS instead of Python or SQL? ... View more

The fact that you keep trying to sugarcoating the issue is actually a perfect reflection or mirror of how SAS company and its tech support deals with problem- Blaming the victims.   If you ever look at other interpreter like Python, you would know that it IS the responsibility for an interpreter to accept whatever code user submitted no matter good or bad. It can respond with error message but should recover when the erroneous code is gone. While for SAS interpreter, it just cannot get itself out from the 'bad code' in this scenario. There is no excuse for such interpreter bug, it is something they should have fixed long time ago. ... View more