The Window for "Opening a Table" is endlessy loading, preventing me to use SAS Studio

[AudeP]

Dears, 

I'm currently working for the SAS Base Certification, and I uploaded the SAS file Salary (from this website : http://www.principlesofeconometrics.com/sas.htm) in order to practice some of the book examples. 
However, in order to see the content of the table on SAS Studio, I double clicked on it to open it, but all I get is a windows for "Opening a Table" that is loading endlessy. I can't use SAS Studio anymore, as this process prevent me to do anything. It's been like that for 3 hours now. 

What could I do to fix this problem? 

Thanks.

[Damo]

Hi @AudeP

Is your current problem related to SAS Studio being unusable or how to use the salary dataset with SAS Studio.

For the later, instead of the double-click, did you try one of those options:

  - declare a LIBNAME and open the dataset from the library listing

  - open the dataset from the Folders listing

If you want to take control of SAS Studio and start from scratch, the quick solution if you're using the SAS Studio Single User version would be to reboot your machine.

Hope that helps.

Cheers,
Damo

[AudeP]

Dear Damo, 

Thank you for your reply. Sadly, the issue is related to SAS Studio being unusable, as the "opening a table" window seems to be indefinitely loading, preventing me to do anything. I'm using SAS Studio for academics, then I can't simply reload my session, and as the parent window is disabled as long as the other window is opened, i can't disconnect from/reconnect to my session.

However, i found a way to get around this issue. I inspected the page to look at the html code related to this endlessly loading window and I deleted the related <div>. I did the same with the part disabling the parent window. Not the best way to solve this problem but it worked. I was then able to work again on SAS Studio. 

It also appears that all the datasets from the url are corrupted, as i got the same issue with some other datasets from this website. Using the LIBNAME statement or going through the folder listing is not preventing the problem from occuring. 

Again, thank you for your reply. 
Cheers, 

AudeP