problem with column type numeric

[apostolish]

Hello,
I'm using JBuilder X (JDK 1.4.2) and SQL Server 2005 (SP2). I connect to a
database using JDBC Driver (sqljdbc.jar).
l execute for example a quey 'select * from table' and i have a column with
type 'numeric' in the 'table'.
My problem it appears when in one or more rows , this column has the value
<null> then the execution of the query fails.
When there is none row which this column has value <null> then i have no
any problem.
I didn't have this problem when i was working with SQL Server 2000 and the
jdbc driver for this.

Thanks in advance
Hatziyannis Apostolis

[Kevin Dean [TeamB]]

apostolish wrote:

>I didn't have this problem when i was working with SQL Server 2000 and the
>jdbc driver for this.

It sounds like a problem with the JDBC driver. Do you have an exception
stack trace when the query fails that you can post?

--
Kevin Dean [TeamB]
Dolphin Data Development Ltd.
http://www.datadevelopment.com/

Please see CodeGear's newsgroup guidelines at
http://support.codegear.com/newsgroups/guidelines

[apostolish]

The window with the error message is:

Error
Execution of query failed

Details
See com.borland.dx.dataset.DataSetException error code: BASE+62
com.borland.dx.dataset.DataSetException: Execution of query failed.
at com.borland.dx.dataset.DataSetException.a(Unknown Source)
at com.borland.dx.dataset.DataSetException.queryFailed(Unknown Source)
at com.borland.dx.sql.dataset.QueryProvider.a(Unknown Source)
at com.borland.dx.sql.dataset.JdbcProvider.provideData(Unknown Source)
at com.borland.dx.dataset.StorageDataSet.a(Unknown Source)
at com.borland.dx.dataset.DataSet.a(Unknown Source)
at com.borland.dx.dataset.DataSet.open(Unknown Source)
at com.borland.jbcl.control.GridControl.openDataSet(GridControl.java:204)
at com.borland.jbcl.control.GridControl.addNotify(GridControl.java:105)
at java.awt.Container.addNotify(Container.java:2049)
at javax.swing.JComponent.addNotify(JComponent.java:4291)
at com.borland.jbcl.view.BeanPanel.addNotify(BeanPanel.java:256)
at java.awt.Container.addNotify(Container.java:2049)
at java.awt.Window.addNotify(Window.java:418)
at java.awt.Frame.addNotify(Frame.java:482)
at java.awt.Window.show(Window.java:459)
at java.awt.Component.show(Component.java:1133)
at java.awt.Component.setVisible(Component.java:1088)
at prog.u.test.CountApplication.<init>(CountApplication.java:37)
at prog.u.test.CountApplication.main(CountApplication.java:52)
Chained exception:
java.lang.NullPointerException
at com.microsoft.sqlserver.jdbc.SQLServerResultSet.getBigDecimal(Unknown
Source)
at com.borland.dx.sql.dataset.JdbcProvider.a(Unknown Source)
at com.borland.dx.sql.dataset.JdbcProvider.c(Unknown Source)
at com.borland.dx.sql.dataset.JdbcProvider.provideData(Unknown Source)
at com.borland.dx.dataset.StorageDataSet.a(Unknown Source)
at com.borland.dx.dataset.DataSet.a(Unknown Source)
at com.borland.dx.dataset.DataSet.open(Unknown Source)
at com.borland.jbcl.control.GridControl.openDataSet(GridControl.java:204)
at com.borland.jbcl.control.GridControl.addNotify(GridControl.java:105)
at java.awt.Container.addNotify(Container.java:2049)
at javax.swing.JComponent.addNotify(JComponent.java:4291)
at com.borland.jbcl.view.BeanPanel.addNotify(BeanPanel.java:256)
at java.awt.Container.addNotify(Container.java:2049)
at java.awt.Window.addNotify(Window.java:418)
at java.awt.Frame.addNotify(Frame.java:482)
at java.awt.Window.show(Window.java:459)
at java.awt.Component.show(Component.java:1133)
at java.awt.Component.setVisible(Component.java:1088)
at prog.u.test.CountApplication.<init>(CountApplication.java:37)
at prog.u.test.CountApplication.main(CountApplication.java:52)

Ο "Kevin Dean [TeamB]" <Kevin.RE...@datadevelopment.com> έγραψε στο
μήνυμα news:xn0fqfuy5121...@www.teamb.com...

[Kevin Dean [TeamB]]

It appears to be a known bug:

http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=2779767&SiteID=17

If you look at the last post, Microsoft has acknowledged the problem, but
also points out that the method getBigDecimal() has been deprecated.
Unfortunately, there is no current work being done on the DataExpress
components, so the alternative might be to change the column type to
Double and see what happens.