Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>I guess this error message is linked to the state of one of your databases. You are using here Jet connections and Access objects, and you might not be able, for multiple reasons (multi-user environment, unability to delete LDB Lock file, etc), to properly close your active database and open another one. So, according to me, the solution is to forget the Jet engine and to use another connexion to update the data in the "other" database.</p> <p>When you say "The dataflow is to update all 'projects' once a month in one database and then make this information available in the other database", I assume that the role of your "Routine" is to update some data, either via SQL instructions or equivalent recordset updates. </p> <p>Why don't you try to make the corresponding updates by opening a connexion to your other database and (1) send the corresponding SQL instructions or (2) opening recordset and making requested updates?</p> <p>One idea would be for example:</p> <pre><code>Dim cn as ADODB.connexion, qr as string, rs as ADODB.recordset 'qr can be "Update Table_Blablabla Set ... Where ... 'rs can be "SELECT * From Table_Blablabla INNER JOIN Table_Blobloblo set cn = New ADODB.connexion cn.open You can here send any SQL instruction (with command object and execute method) or open and update any recordset linked to your other database, then cn.close </code></pre> <p>This can also be done via an ODBC connexion (and DAO.recordsets), so you can choose your favorite objects.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload