I have a connection to a table which I am inputting using you 3.0 version. This table is also accessed using an application. The application registers that there is a new record, but it can not move to that new record.
If I leave the application and reopen, then the record is not accessible.
Any thoughts?
|
>The application registers that there is a new record, but it can not move to
>that new record.
If it's a Foxpro application, you should use lockType=Foxpro connection property so that both of Java and your Foxpro application can see each other lock.
|
|
What is the separator between the URL and the variable lockType=Foxpro. Is it a question mark "?"
|
jdbc:dbf://bestdevwp02:8029///vmmakore/MitekVisaliaTest/data/Database?lockType=Foxpro
This is my URl in the URL Info of the Config Server. I have also tried to att that lockType to the data base URL as well. Neither change worked. Any other suggestions? I am using version DBF_JDBC30.zip dated back to 6/12/2006.
I have had no problem with it since then, cause I have always done reads only from this system, but now I am trying to input data from it.
|
������I am using version DBF_JDBC30.zip dated back to 6/12/2006.
Very old, but should work normally with Foxpro.
>The application registers that there is a new record, but it can not move to
> that new record.
>If I leave the application and reopen, then the record is not accessible.
>cause I have always done reads only from this system, but now I am trying to input data from it.
Please check also whether your older Foxpro application runs on multi-user mode. Whether it's a Foxpro or Clipper applcation.
|
|
I have been reading the documentation and I noticed a reference to JNIFile.dll. Is this necessary for the lockType=Foxpro to work?
|
>I have been reading the documentation and I noticed a reference to JNIFile.dll.
>Is this necessary for the lockType=Foxpro to work?
Checked.
v3.0.040 will detect OS version, and choose the suitable JNI lock or NIO lock for Xbase compatible lock on Linux/Unix.
v2.1.97 supports java.nio.channels.FileLock for JDBC3.0 on JDK1.4.X and JDK1.5.X so that JNIFile.zip become unnecessary.
You should be using v2.3 .
|
|
So yes it needs the DLL or No it does not?
|
Ok I figured it out. I downloaded your latest 3.0 version and ran it on my server with no parameters and everything worked. There must have been a bug fix from the version 3.0 that we purchased and the latest release on your web site.
How can I get my version upgraded?
|
|
How can I upgrade to the latest version of the 3.0? I have an older 3.0 version that was not working with Foxpro locking.
|
>ran it on my server with no parameters and everything worked
You mean without lockType=Foxpro connection property?
|
No I mean, I have purchased a v3.0 a while ago (6/12/06). I have tried the lockType=Foxpro on it and it does not work. I downloaded the latest 3.0 version and the lockType=Foxpro does work (it is only a 30 day eval version).
So how can I get a released version of the latest 3.0 version.
|
Main
webmaster@hxtt.com