I'm not absolutely sure but I think it is probably sashome\SASFoundation\9.4\core\sasexe\sasoact.exe. It's worth a try, you can always change it again if it doesn't work! ... View more

If you select Open with, Choose another app... you will get a list of alternatives, but there should be a tick box or a button (depending on your version of Windows) always to use the application you use. If you choose SAS and select the "Always" option it should always open in SAS when you double-click a .sas file. ... View more

I think we need a bit more to go on. What do you get in the logs when you try to load data unsuccessfully? ... View more

Ah, that makes sense. Thanks @ronf_sas  ... View more

Definitely. When we upgraded, we had all kinds of problems until we disabled our AV software, from some processes being blocked to others taking much longer than they should because of the AV software scanning in real time. ... View more

If you don't have the database specified in the DSN, it'll use the master database by default. Check out the contents of your odbc.ini file (if you're not on a Windows machine). Or else use a complete connection string rather than specifying a DSN. https://www.connectionstrings.com/microsoft-odbc-driver-13-for-sql-server/ has some guidance on this. ... View more

It would be worth trying an ODBC special catalog query:     proc sql; connect to odbc as MyODBCName (dsn="MyODBCName" user="username" password="password"); select * from connection to MyODBCName ( ODBC::SQLTables(,"dbo") ) ; disconnect from MyODBCName ; quit; It should produce a list of the tables in the dbo schema. If you want the tables from all schemas then remove the contents of the brackets in the  ODBC::SQLTables  statement. I've found this an invaluable tool for investigating connection problems to ODBC data sources. More information in the documentation here:   https://documentation.sas.com/doc/en/pgmsascdc/9.4_3.5/acreldb/p1f29m86u65hken1deqcybowtgma.htm    ... View more

Hi Siddhu Something we see sometimes with EG with a dialogue is that it opens on a different, non-existent, screen. Happens when you've had more than one screen in the past and now fewer. It might be this that is happening. Try the following when you try to join tables and EG appears to be hung: Press ALT-Space, M, followed by one of the cursor keys. Now move your mouse, and you may well find that the Tables and Joins dialogue pops onto your mouse pointer. You can then simply left-click to position the dialogue where your mouse pointer is.   Hope this helps ... View more

That's a bit surprising with the advanced search. My initial thought was that it might have been an upper/lower case issue but it seems to be case-insensitive on our system. The other thing I've used to good effect, not having access to the Metacoda plugins, is the metadata browser in a desktop SAS session (Solutions>Accessories). It's a good way of seeing the metadata structure. I note your comments about using IWA and connections to SQL Server being blocked. I seem to remember that the issue here is that authentication isn't propagated through to the database. It's one reason why we don't use IWA. We are also on Windows Server 2019 and have many connections to database servers. We're able to use the DefaultAuth authdomain for the SQL Server ones but because we aren't using IWA the authentication is done for each connection. ... View more

Thanks, that did the trick. I wondered if there was a way to do it programmatically but I haven't delved  much into changing metadata that way. ... View more

I'm not sure this would work. What goes in the quotes should simply be a path. If you need to store the data on a different machine I think you'd need to look at using a shared drive (Windows) or a Network Filesystem (UNIX/Linux). In a mixed environment, the two OS types can be persuaded to use each other's drive share protocols. I'm very open to being corrected...!  ... View more