Our FoxPro tables are updated from foxpro applications used by numerous other users. Our new application, which uses hxtt dbf running on a windows machine which is then accessed by a glassfish application server. This glassfish server acts as the host for a number of webservices which query data from the foxpro database.
Any updates made to the foxpro data can take a long time to flow to the webservices which request the data, to the point of making the data retrieved by the webservice valueless.
Is there some way to turn off the caching of data (whether in the hxtt server or the glassfish server)?
Thanks.
|
|
You should use lockType=Foxpro connection property in your jdbc url. It's at here.
|
Is lockType=VFP also an option here? I'm assuming this is a lock for VisualFoxPro, which is the application framework that is updating the foxpro tables.
I am using this as one of the connection parameters in my glassfish server where I pool the connections to the hxtt server. Is this the correct place for this?
|
|
Yeah. You can use lockType=VFP too.
|
|
Thanks. I'll follow up if the solution isn't resolved.
|
Main
webmaster@hxtt.com