Linked table |
Patrick |
2013-11-12 06:06:37 |
Hello,
I'm using a *.mdb file with many tables. Some of them are in fact links to tables in other *.mdb files.
Everything works fine when using HXTT on Windows, but on Linux the linked tables cannot be found, because the link is an absolute path like "C:\data\other.mdb".
I couldn't find a way on Access to use relative paths for linked tables.
Do you know how to solve this problem?
Thanks,
Patrick
|
Re:Linked table |
HXTT Support |
2013-11-12 06:20:01 |
>because the link is an absolute path like "C:\data\other.mdb".
>I couldn't find a way on Access to use relative paths for linked tables.
Yeah. Whether you have copied the other.mdb into the same directory of your .mdb file?
|
Re:Re:Linked table |
Patrick |
2013-11-12 06:24:50 |
Yes I did.I still get the error:
java.sql.SQLException: Failed to load database M:\bpl2000data\ticketData:java.io.FileNotFoundException: M:\bpl2000data\ticketData.mdb (No such file or directory)
at com.hxtt.global.SQLState.setNextException(Unknown Source) ~[accessjdbc4-5.1.178.jar
|
Re:Re:Re:Linked table |
HXTT Support |
2013-11-12 06:51:33 |
>Yes I did.I still get the error:
It's normal since Linked table used absolute path. We will provide a guess path solution so that it's possible to access linked table with absolute Windows path information on Linux.
|
Re:Re:Re:Re:Linked table |
HXTT Support |
2013-11-14 00:08:36 |
Supported. Please download the latest package.
|
Re:Re:Re:Re:Re:Linked table |
Patrick |
2013-11-14 00:17:00 |
Great! How must it be configured?
|
Re:Re:Re:Re:Re:Re:Linked table |
HXTT Support |
2013-11-14 00:25:51 |
Needn't set. It will guess path. For instance, "C:\data\other.mdb", and you are using jdbc:access////home/user/, it will searh it as /home/user/other.mdb or /home/user/data/other.mdb .
|
Re:Re:Re:Re:Re:Re:Re:Linked table |
Patrick |
2013-11-18 08:45:47 |
Thanks for your message.
I can't seem to be able to make it work. Here's my config:
datasource url = jdbc:access:////Users/pat/Documents/workspace-spring/data/bpl2000data.mdb
second file is in the same folder: /Users/pat/Documents/workspace-spring/data/ticketData.mdb
Table link inside first file to second file is: M:\bpl2000data\ticketData.mdb
|
Re:Re:Re:Re:Re:Re:Re:Re:Linked table |
HXTT Support |
2013-11-18 19:31:48 |
Fixed. Please download the latest package.
|
Re:Re:Re:Re:Re:Re:Re:Re:Linked table |
Patrick |
2013-11-20 00:12:43 |
Ok it works with version 5.1.184.
Thanks!
|
CACHE problem |
Patrick |
2013-12-04 06:47:43 |
Hi,
There's a bug when the linked table gets updated by another process: changes are not reflected when following link.
It looks like the cache is hit, instead of the file.
Thanks for your help,
Patrick
|
Re:Re:Re:Re:Re:Re:Re:Re:Linked table |
HXTT Support |
2013-12-05 05:58:26 |
>There's a bug when the linked table gets updated by another process: changes are not reflected when following link.
>It looks like the cache is hit, instead of the file.
Try connection property:
lockType=ACCESS
refreshInterval=0 at here
|
Re:Re:Re:Re:Re:Re:Re:Re:Linked table |
Patrick |
2013-12-05 08:21:06 |
With lockType=ACCESS, it's impossible to retrieve data from linked table as soon as another Access client modifies it.
Data is completely strange, it's as if the pointer in the db file is at the wrong place.
|
Re:Re:Re:Re:Re:Re:Re:Re:Linked table |
HXTT Support |
2013-12-05 16:34:34 |
>With lockType=ACCESS, it's impossible to retrieve data from linked table as soon as another Access client modifies it.
MS Access client should be opening exclusively that table.
Then remove lockType conneciton property, and try J2ME=true and delayedClose=0.
|
Re:Re:Re:Re:Re:Re:Re:Re:Linked table |
Patrick |
2013-12-06 00:19:13 |
Thanks for your message.
With J2ME=true, it's incredibly slow (a simple SELECT takes 200 sec, the same SELECT takes 1.5 sec without this parameter).
|
Re:Re:Re:Re:Re:Re:Re:Re:Linked table |
HXTT Support |
2013-12-06 01:29:25 |
Because it need a way to know whether that data has been modified:(
Usually lockType=ACCESS and refreshInterval=n can work perfectly with concurrent data modification according to MS Access lock mechanism. But your Access client seems to use database exclusively.
J2ME=true can see data modification ASAP, but can't do concurrent data change. If it can work for you, we can try to find a better solution to use partly cache.
|
Re:Re:Re:Re:Re:Re:Re:Re:Linked table |
Patrick |
2013-12-06 01:33:47 |
Ok thanks for your answer. All our clients are MS ACCESS 2013, and of course our java server.
We absolutely need concurrent data change.
Let me do more tests with lockType=ACCESS and get back to you.
Thanks,
Patrick
|
Re:Re:Re:Re:Re:Re:Re:Re:Linked table |
Patrick |
2013-12-09 08:45:57 |
OK it looks like this problem has nothing to do with linked tables.
This is what I found:
Test consists in opening a db with MS ACCESS 2003 and with HXTT jdbc driver (with lockType=ACCESS).
a) Modify with HXTT and see if modification appears in MSAccess
b) Modify with MSAccess and see if modification appears in HXTT
---- TEST 1 OK-----
Access JDBC Driver 4.1 version 5.1.136
Everything looks good
---- TEST 2 KO-----
Access JDBC Driver 4.1 version 5.1.141
a) is ok
b) is KO: HXTT driver unable to read db, as if pointer in data file is at a wrong place.
All versions after 5.1.141 have the same problem.
|
Re:Re:Re:Re:Re:Re:Re:Re:Linked table |
HXTT Support |
2013-12-09 21:01:52 |
Thanks for your valuable response. Please redownload it.
|
Re:Re:Re:Re:Re:Re:Re:Re:Linked table |
Patrick |
2013-12-10 00:14:24 |
Test b) doesn't work with version 5.1.187. I still got errors where HXTT driver tries to read wrong columns, like this:
"SQLException: Failed to get a short value from java.lang.String: ??0000275004"
That value is from another column.
|
Re:Re:Re:Re:Re:Re:Re:Re:Linked table |
HXTT Support |
2013-12-10 01:13:03 |
>I still got errors where HXTT driver tries to read wrong columns, like this:
Please let us see your test sample or test step.
|
Re:Re:Re:Re:Re:Re:Re:Re:Linked table |
Patrick |
2013-12-10 01:33:09 |
Ok I have a test db. How can I send it to you?
|
Re:Re:Re:Re:Re:Re:Re:Re:Linked table |
HXTT Support |
2013-12-10 03:21:20 |
support at hxtt.com
|
Re:Re:Re:Re:Re:Re:Re:Re:Linked table |
HXTT Support |
2013-12-10 07:37:08 |
Recurred and fixed. Please download it.
|
Re:Re:Re:Re:Re:Re:Re:Re:Linked table |
Patrick |
2013-12-10 08:51:35 |
Hi,
It's better now, but as I was playing around (making concurrent modifications with HXTT and MSACCESS), one time I got this error:
Caused by: java.sql.SQLException: Inner error on query with index expression
at com.hxtt.global.SQLState.SQLException(Unknown Source)
at com.hxtt.sql.r.a(Unknown Source)
And then everything was stuck. I had to restart the java server.
Sadly I'm not sure how I triggered this problem.
P.S. The new download has the same version 5.1.187. Is it the correct one?
|
Re:Re:Re:Re:Re:Re:Re:Re:Linked table |
HXTT Support |
2013-12-11 01:34:23 |
>Caused by: java.sql.SQLException: Inner error on query with index expression
Checked. Please download the latest package.
|
Re:Re:Re:Re:Re:Re:Re:Re:Linked table |
Patrick |
2013-12-11 03:00:21 |
Still older version (5.1.187 compiled december 10) on server.
|
Re:Re:Re:Re:Re:Re:Re:Re:Linked table |
HXTT Support |
2013-12-11 03:49:08 |
It's v5.1.188 in fact. Please download it.
|
Re:Re:Re:Re:Re:Re:Re:Re:Linked table |
Patrick |
2013-12-11 05:12:36 |
I'm not able to get this version.
I go to http://www.hxtt.com/download.jsp
Then I download "Access JDBC 4.1 Package for JDK1.7.X "
Then I run java -classpath Access_JDBC41.jar com.hxtt.sql.access.AccessDriver
I still get "HXTT Access JDBC4.1 Driver (Version 5.1.187) Compiled: December 10, 2013"
|
Re:Re:Re:Re:Re:Re:Re:Re:Linked table |
HXTT Support |
2013-12-11 05:38:30 |
Checked. Yeah. Now I have reupload it.
|
Re:Re:Re:Re:Re:Re:Re:Re:Linked table |
Patrick |
2013-12-11 06:47:31 |
..... still the old version ....
|
Re:Re:Re:Re:Re:Re:Re:Re:Linked table |
HXTT Support |
2013-12-11 16:04:05 |
Checked again. Sorry. Now it's right file.
|
Re:Re:Re:Re:Re:Re:Re:Re:Linked table |
Patrick |
2013-12-12 01:23:51 |
Ok thanks I got it. I will test for a few days and get back to you
|