- This topic has 6 replies, 3 voices, and was last updated 20 years ago by
.
-
Posts
-
I have a table that has a LONGCHAR field ‘description’ that has about 500 characters in some of the records.
In the dBase explorer, when I run the following
‘select ID, name, description from tNaspStandard group by name, ID, description’
I don’t get the entire desciption field returned.
For development, I am connected to a MSAccess dBase. Is this an MS issue or am I screwing something up?
Thanks…
Can you please post all the information we request in the [URL=http://www.myeclipseide.com/PNphpBB2+file-viewtopic-t-393.html]Posting Guidelines[/URL] thread at the top of this forum? That will give us some context so that we can determine if this is an installation issue, a configuration problem, or a bug. Thanks.
Also let us know what driver and version of the driver you are using.
Sorry about that, I should have know better. If you need anything else, just let me know…
I’m running XP Pro
Eclipse 3.0.1
MyEclipse 3.8.2+QF2004120
Java version j2sdk1.4.2_05
Tomcat version 5.0.28
DBase – Access 97Do you see any errors in the error log after running the query? Probably not, since the query seems to complete, but it is worth double-checking. When you select the table in the browser, what is the column definition in the Table Info View show? Also, it would be worth searching any forums available for the JDBC driver you are using for reports of similar problems. I do not think this is a problem with the plugin, sounds like something related to the driver.
There isn’t anything logged as you suspected.
Looking at the Table Info, it shows correctly that the Data Type is LONGCHAR and the Size is 2147483647.
As far as the driver I’m just using the JDBC ODBC Bridge. The class name is sun.jdbc.odbc.JdbcOdbcDriver.
Has anyone else out there experienced issues with this driver? Is there a different one I could be using?
The size is highly suspect – is this Access’s excuse for clob/blob? If so, the driver may be only returning a portion of the value when ResultSet.getString(n) is used, and not the more typical InputStream read operation to retrieve all the results. Please investigate this with the driver forums (or whatever Microsoft offers for support of the driver) and let me know. There may be little or nothing we can do if the driver is not reporting an adequate conversion for a LONGCHAR, although we are not above special-casing where justified.
Thanks for your time. I’ll start digging through the other forums. I was kind of hoping to get lucky, you guys usually have all the answers…
I’m definately not asking for a special case kind of thing. I’ll be deploying on Oracle so I’ll live with a partial query result until I find something from MS.
Thanks again…
