ver: 7.1.1
This is yet another report of what we have already reported 2+ times:
http://www.allroundautomations.com/cgi-bin/ultimatebb.cgi?ubb=get_topic;f=3;t=003801;p=0#000000
http://www.allroundautomations.com/cgi-bin/ultimatebb.cgi?ubb=get_topic&f=4&t=000106
At those places it was classified as a bug by the admin and we were told: ~"it'll be addressed".
Half a year passing by and in the meantime I thought I'd try another way and as there are a couple hundred of developers worldwide in the company I work for and we have an unlimited site license for PL/SQL Dev I contacted our internal support for some help and they said: You should keep using ver 5, or for editing you can use Visual Slickedit.
Not a nice perspective :-/
This time I'm trying to get a little more definitive reply:
Approx by what time can we expect a fix for this bug?
This is yet another report of what we have already reported 2+ times:
http://www.allroundautomations.com/cgi-bin/ultimatebb.cgi?ubb=get_topic;f=3;t=003801;p=0#000000
http://www.allroundautomations.com/cgi-bin/ultimatebb.cgi?ubb=get_topic&f=4&t=000106
At those places it was classified as a bug by the admin and we were told: ~"it'll be addressed".
Half a year passing by and in the meantime I thought I'd try another way and as there are a couple hundred of developers worldwide in the company I work for and we have an unlimited site license for PL/SQL Dev I contacted our internal support for some help and they said: You should keep using ver 5, or for editing you can use Visual Slickedit.
Not a nice perspective :-/
This time I'm trying to get a little more definitive reply:
Approx by what time can we expect a fix for this bug?