I've noticed that the run-time driver appears to cache an entire Excel document in memory across connections. If I change the Excel document, the changes are not reflected in the new JDBC connection obtained.
At this point the only way to discover the changes is to restart the virtual machine. Is there a mechanism to flush the in-memory cache of the file when a connection is closed?
Thanks,
Ed
|
|
You can try delayedClose=-1 connection property so that it can reload. BTW, HXTT Excel doesn't support concurrent write when MS Excel is writing the same xls at the same time.
|
Thanks! Working for me now.
|
Main
webmaster@hxtt.com