Page 1 of 1

Some errors...

Posted: Thu 27 Oct 2005 06:24
by HalfLife
I use OraDeveloper Studio 1.0.3.0.

Oracle server version is 9i.
When I use direct connection(without Oracle Client), retrieved data is not shown correctly.
Data was '1234', but shown as '123'.
I can see data correctly when use Oracle Client.

And 'Help' menu not available except 'About...'.
I cannot use 'Help' menu.
I have to access 'OraDeveloper.chm' directly to see help file. :(

Posted: Fri 28 Oct 2005 15:16
by Duke
When I use direct connection(without Oracle Client), retrieved data is not shown correctly.
Could you, please supply with the table information?
And 'Help' menu not available except 'About...'.
Check if the registry key
HKEY_LOCAL_MACHINE\SOFTWARE\CoreLab\OraDeveloper
contains HelpFile value with full path to the chm file.

Posted: Fri 04 Nov 2005 04:34
by HalfLife
This is table info.

Code: Select all

SQL> desc tbl_clients;
 SECRETKEY    NOT NULL     VARCHAR2(16)
 HOSTNAME                  VARCHAR2(32)
 STATUS                    VARCHAR2(3)
 NOTE                      VARCHAR2(64)
 IPADDR       NOT NULL     VARCHAR2(15)
Click this link to see Sreen Shot
1-1. Retrived data using Oracle Client
Correct.

1-2. Edit table using Oracle Client
Wrong result !!

2-1. Retrived data using Direct connection
Wrong result !!

2-2. Edit table using Direct connection
Wrong result !!

When I use direct connection(without Oracle Client), retrieved data is not shown correctly.
As I see...
If table field length is 4 and the data length is 4, OraDeveloper Studio eliminates last charactor.

When I use "Edit Table", always WRONG !! (Length & Nullable)

Oh... There is no registry key
"HKEY_LOCAL_MACHINE\SOFTWARE\CoreLab\OraDeveloper.
How to create it ? I want to know key name, type and value.

Posted: Fri 04 Nov 2005 04:59
by HalfLife
I tested with OraTools...

Everythings OK with OraTools except overflow. :!:
OraTools cannot display big integer, but OraDeveloper can.

Posted: Mon 07 Nov 2005 07:43
by Duke
We've found the problem with direct mode and VARCHAR fields. The problem will be fixed in the nearest release of OraDeveloper.