juliepaynemft Group

Public·285 members

June 14, 2023

File: MIST-1.0.3-pc.zip ...

remap (since UCanAccess-2.0.2): it allows to remap the paths to one or more external linked databases. The syntax is: jdbc:ucanaccess://C:/db/;remap=& e.g., jdbc:ucanaccess://C:/db/main.mdb;remap=c:\db\linkee1.mdbC:\pluto\linkee1.mdb&c:\db\linkee2.mdbC:\pluto\linkee2.mdb Original path and new path must be separated by '', different pairs must be separated by '&'. mirrorFolder (since UCanAccess 2.0.9.3): it allows users to set the directory in which the mirror db will be created. It forces memory=false. Simply use mirrorFolder=java.io.tmpdir in order to specify the system temp folder for that. keepMirror (since UCanAccess 2.0.2): keeps the HSQLDB mirror database after the VM ends so it can be reused by subsequent VM processes. It forces memory=false. In other words, using this parameter, the time-expensive process of creating and populating the database hsqldb (with memory=false), is executed only once. jdbc:ucanaccess://C:/db/main.mdb;keepMirror=C:/db/mirrorName Reusing the same keepMirror setting (e.g. keepMirror=C:/db/mirrorName) at the next VM process execution allows you to dramatically reduce the time of first connection. It should be used only with very large databases (e.g., 1GB with many binary OLE objects) and when: You have to change the default memory=true setting because you can't allocate sufficient JVM heap space (Xmx VM paramenter).
UCanAccess takes too much time to establish the first connection (because it's populating the HSQLDB mirror database).

Caution! - If the access database is modified by a different program (so not using UCanAccess) after the HSQLDB creates the mirror database, UCanAccess recreates and repopulates the whole mirror database for avoiding unchecked misalignments. columnOrder (since UCanAccess 2.0.9): use the "DISPLAY" order of columns with SELECT * statements. ("DATA" order is still the default). jdbc:ucanaccess://c:/db/cico.mdb;columnOrder=DISPLAY Note that once a column order has been set on the first connection to a given database, that setting will be the same for all the following connections to that database, in the whole VM life. concatNulls (since UCanAccess 3.0.0): controls the behaviour of all concatenation operators (&,+,) with null values: null & 'thing' -> 'thing'. (It gave null prior to version 3.0.0.) null + 'thing' -> 'thing'. (It gave null prior to version 3.0.0.) If you want to switch to the old behaviour, you have to set the new connection property concatNulls=true. preventReloading (since UCanAccess 3.0.0): optimize the reloading of db instances. If and only if you're sure that your db can be accessed by the MS Access GUI and just one JVM instance (using UCanAccess), you can use the connection parameter preventReloading=true. It avoids the data being reloaded when they aren't actually changed by the GUI. jackcessOpener (since UCanAccess 0.0.2): in order to use Jackcess Encrypt extension, you can specify a class that implements the net.ucanaccess.jdbc.JackcessOpenerInterface interface (in that case you need additional jar files in your classpath: a version of jackcess-encrypt.jar and all related dependencies). The following example shows a custom integration with Jackcess Encrypt for opening a Money (.mny) file: