I'm trying to use this driver in the Java Studio Creator 2 product. I'm connecting to a Visual Foxpro 9 database. Almost everything works just fine, but I can't view my main customer table. This table has an index set in the customer.cdx file that is looking for a field called naccount_no. Obviously this is greater than 10 characters. When I look at the table names in the the Creator software this was truncated to naccount_n. Is there a way to make the driver ignore any preset indexes and create my own? Here's the actual error I get...
Index I:\UB\CUSTOMER.CDX should have an invalid index expression naccount_no for NOT DELETED(), since failed to find column naccount_no !
select ccust_key from ubs1.customer
Any help would be appreciated - Thanks
It seems that you're asking a question about HXTT DBF package, not DB22DBF. What's your HXTT DBF version? Passed test in my test case. HXTT DBF supports long column name for VFP 9.0, and can find the long column name in ubs1.dbc.
Thanks for the response, here's what I have...
I downloaded and tried HXTT DBF v3.1. I pointed my Java Creator 2 program to the DBF_JDBC30.jar file and successfully connected to the database. I set my URL to jdbc:dbf:/I:/ub/
If I bind the data to a button by adding a Data Provider, none of my customer columns will appear due to that error message. If I right click on the sessionbean "customerRowSet: "Select * From Customer" and choose "Edit SQL Statement" I can then view the table and each column. In this view the column names are definitly truncated to 10 characters. Am I using an old driver,the wrong URL, or the wrong sql syntax? If so any advice is very welcome.
>If I bind the data to a button by adding a Data Provider, none of my
>customer columns will appear due to that error message.
How to recur that error? With HXTT DBF v3.1, we can't see error message like : Index I:\UB\CUSTOMER.CDX should have an invalid index expression naccount_no for NOT DELETED(), since failed to find column naccount_no
>In this view the column names are definitly truncated to 10 characters.
Yeah. Because old Xbase support at most 10 character as column name, VFP support 128 character as column name but in fact it used still 10 character as column name, and stores the long column name information in ubs1.dbc . You can use naccount_no or naccount_n in your sql.