Hi Diego,
The access violation in your 2nd screenshot is fixed in the beta (available here now) and 16.0 (available here April 26th)
I just opened a tnsnames.ora using version 15.1 and it is working OK for me. I'll be happy to try it with your tnsnames.ora (or even a small one that reproduces the problem, feel free to put in fake service names, etc) if you send it to me: john.dorlon@quest.com
