BookmarkSubscribeRSS Feed

Using EG is like walking on glass shards, so I will not attempt to list all the deep cuts and all the paper cuts one has to continuously deal with. Still, one is annoying and repetitive enough that I must take the time to raise it here:

 

aaa1.PNG

 

When deleting a table, one is sometimes told that the table is locked, as seen above.

 

The table is not visible in the process tree even though it is opened (without being identified) by one of the programs, and the easiest way is then to go back to the process flow view, search for the table somewhere in the flow, delete its shortcut there, and then one can delete the table proper.

 

Please provide a prompt instead of this ludicrous "unexpected error".

 

 

 

19 Comments
JuanS_OCS
Amethyst | Level 16

Great news, thanks @Casey_SAS !

ChrisNZ
Tourmaline | Level 20

Thank you  @Casey_SAS !

 

Can I please ask that you also consider providing a way to see an up-to-date log and to a way to see EG's process number?

 

DaveShea
Lapis Lazuli | Level 10

Hi Casey,

 

Your change of status notification for this idea to "under consideration" is great news. Thank you, this is what puts SAS streets ahead of, ahem, other software vendors.

 

Downunder Dave.

agoldma
Pyrite | Level 9

I know that this idea is about datasets, not about the EGP project files, but I would like to request that SAS-EG also not lock the project files when those files are READ-ONLY.

If I make any other file READ-ONLY in Windows, and someone opens that file, I can still delete that file even while it's open. However, this doesn't work for EGP project files.

PhilC
Rhodochrosite | Level 12

@ChrisNZ , Was a form of this request implemented in EG 8? I think so.

Kurt_Bremser
Super User

@PhilC EG 8 does now close datasets in the background after a rather short period of time. That reduces the number of collisions quite nicely.

PhilC
Rhodochrosite | Level 12

@Kurt_Bremser there IS an option in EG8 under Options > Data > Performance labelled "Unlock all open data before running";  this is along with the option "Unlock open data after inactivity (minutes)".  I didn't have time to look it up before.  

 

but maybe after reading this again, I'm thinking it might be a function of the OS that Chris is complaining about.  I know I close files and delete files in WIN 10 and the OS takes time to register the file's non-existence sometimes...  I wonder.

ChrisNZ
Tourmaline | Level 20

 > delete files in WIN 10 and the OS takes time to register the file's non-existence sometimes.

 

@PhilC Shush... @Kurt_Bremser will not put up with the nonsense of calling WIN 10 an OS...  🙂

Kurt_Bremser
Super User
🙂