unhandeld exception in OraDeveloper Studio Trial

Discussion of open issues, suggestions and bugs regarding database management and development tools for Oracle
Post Reply
glennfr

unhandeld exception in OraDeveloper Studio Trial

Post by glennfr » Mon 12 Dec 2005 10:56

When I open a package (body or declaration) and ther was already something open (results of a table, a view, ...) then I get an unhandled exception and the program is terminated. The message is "'438' is not a valid value for 'value'. 'value' should be between 'minimum' and 'maximum'." The number change every time.

I don 't have the problem when I just started OraDeveloper Studio and then open a package but only when I did first something else.

Duke
Devart Team
Posts: 476
Joined: Fri 29 Oct 2004 09:25

Post by Duke » Tue 13 Dec 2005 10:01

We are unable to reproduce the problem. Could you supply us with following information?

1. Full version of the product (including build number). It's in About window.
2. Version of the .NET Framework that is installed on your machine
3. Version of Oracle server you are using
4. Version of Oracle client software, if you are not in Direct mode
5. Connection string of the database connection you are using
6. Steps to reproduce the problem
7. Optional additional information

glennfr

Post by glennfr » Wed 14 Dec 2005 11:01

1. Full version of the product (including build number). It's in About window.
version 1.0.2.0

2. Version of the .NET Framework that is installed on your machine
.Net Framework 1.1 version 1.1.4322 SP1

3. Version of Oracle server you are using
Oracle9i Enterprise Edition Release 9.2.0.1.0

6. Steps to reproduce the problem
* Retrieve/edit data from a table or an other object but not the package
* Double click on a procedure from a package and than I get the error

7. Optional additional information

The package have 7609 lines

Duke
Devart Team
Posts: 476
Joined: Fri 29 Oct 2004 09:25

Post by Duke » Thu 15 Dec 2005 07:35

We are working on the new version of OraDeveloper Studio. According to tests it does not contain this problem. Soon this version is to be released.

Post Reply