Note that there are some explanatory texts on larger screens.

plurals
  1. POAccess application crashing on ME.[ControlOrFormName] on some machines
    text
    copied!<p>I've got a hairy one for you folks:</p> <p>We are using Oliver's excellent script as posted here <a href="https://stackoverflow.com/questions/187506/how-do-you-use-version-control-with-access-development">How do you use version control with Access development?</a>) to save our Access application as text, so it could be revision-controlled using Subversion.</p> <p>The application consist of a front- and back-end, with only the frontend being decomposed using the script. Whenever a dev wants to work on the application, he'll get the latest revision from the repo, then run the script to recreate the frontend on a new mdb file (or overwrtite an existing one; it doesn't affect the issue here.)</p> <p>Now, for some recreated MDBs, the program will crash on VBA code where an object is refered in a form's code as Me.FieldOrControlName and wont run till its changed to Me![FieldOrControlName].</p> <p>There is no spaces or otherwise forbidden characters in the FieldOrControlName name. More often than not, FieldOrControlName is the same for both the form's control and the form's recordsource's field (bad practice, I know, but please bear with me...)</p> <p>It has been tried with both the AutoCorrect names option activated and disabled, if it related in anyway.</p> <p>Now, If I recreate the frontend from the repository's source on my machine, everything is fine; if Denis recreates it using the same sources on his machine, he gets the bug.<br> If he then take my rebuilt frontend and copy it on his machine, it works fine, which feels to me as a Access-level default value for language or format compatibility that is present in the mdb recreated from my computer. Or could it be related to a service pack / version difference between machines? We seem to have a mix of SP2 (11.6566.8333) and SP2 (11.6566.6568).</p> <p>Any insight would be welcome, as ever,</p> <p>Regards, Pascal</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