Hi,
We have an application written in javascript, using your driver to communicate with a foxpro application in the backend. We give the server path to our application server to communicate with the backend database. The problem is when we try to start the service, if at that point there is a DBF file in the foxpro application path that has got an exclusive lock on it by another user or application, the server can not make the connection, although the file is not even going to be used by our application.
I was wondering if there is a way that we can exclude some dbf files with certain naming convention from being touched by hxtt driver. These files are temp files that are being created by users at some point and will be deleted after, and they don't have anything to do with any other user who is going to use the application, so there is no reason for it to be accessed.
Thanks,
Siavash
|
> The problem is when we try to start the service, if at that point there is a DBF file in the foxpro application path that has got an exclusive lock on it by another user or application, the server can not make the connection, although the file is not even going to be used by our application.
You needn't use that DBF or dbc in your JDBC url. You can use "select * from dbcName1.tableName1" to visit it. If your tableName1 table hasn't longer column name, you can even use "select * from tableName1" directly.
>I was wondering if there is a way that we can exclude some dbf files with certain naming convention from being touched by hxtt driver.
If you doesn't use those files, then HXTT DBF should not access them.
|
> The problem is when we try to start the service, if at that point there is a DBF file in the foxpro application path that has got an exclusive lock on it by another user or application, the server can not make the connection, although the file is not even going to be used by our application.
You needn't use that DBF or dbc in your JDBC url. You can use "select * from dbcName1.tableName1" to visit it. If your tableName1 table hasn't longer column name, you can even use "select * from tableName1" directly.
This is the url we are using to access the database: jdbc:DBF:/T:/foldername/xyz?loadIndices=true;lockType=FoxPro
which xyz is the application folder that has all the DBF files etc. in it. We don't specifically mention any DBF file/files to be used or not.
|
delayedClose: Indicates the delayed seconds for close transaction. That option is used to avoid frequent close/open table operations for following sqls. Automatic temporary index is disabled when delayedClose<=60s. You can use 0~120 seconds. Default: 3.
You can use delayedClose=0 if you wish to release that table ASAP.
|