Install Add-In as compiled version (accde)

[josef-poetzl]

I like to install add-ins as accde so that the built-in error handling runs stably, since I usually develop with option "Break on All Errors".

This feature is easy to install:

Public Function InstallVCSAddin(Optional ByVal CreateCompiledVersion As Boolean = False) As Boolean
...

    If CreateCompiledVersion Then
        CreateAccde strSource, strDest
    Else
        FSO.CopyFile strSource, strDest, True
    End If
    
....

Private Sub CreateAccde(ByVal SourceFilePath As String, ByVal DestFilePath As String)
 
    Dim FileToCompile As String
    Dim AccessApp As Access.Application
 
    FileToCompile = DestFilePath & ".accdb"
   
    FSO.CopyFile SourceFilePath, FileToCompile, True
   
    Set AccessApp = New Access.Application
    AccessApp.Visible = True
    'create accde
    AccessApp.SysCmd 603, (FileToCompile), (DestFilePath)

    FSO.DeleteFile FileToCompile, True

End Sub

see: https://github.com/josef-poetzl/msaccess-vcs-addin/tree/Create-compiled-add-in-file
Note: In the form frmVCSInstall I added a checkbox for the selection if an accde should be created.

[joyfullservice]

Interesting... Personally, I prefer the ability to debug and step through code in the add-in project. You are certainly welcome to run the add-in as an accde, but I believe the greater number of users prefer the accda format. (Others can feel free to chime in here and we can see what the response is like from the developer community.)

[mwolfe02]

I have to admit, I find it jarring when I switch to the code editor and the version control addin project is selected instead of the project I'm working on. That might be because I've never worked with an .accda before. I like the idea of being able to jump into the add-in code if there was a problem, but 99% of the time I would prefer if it stayed out of the way entirely. I'm still in the experimentation phase with the add-in, as I'm continuing to use my in-house version control script in production. That said, I've already made the decision to switch to the add-in, so I will likely be working with it much more in the near future.

I may adapt to having it available in VBA as I work with it more...or I may come back to Josef's solution and compile it to an accde to keep it out of sight and out of mind (assuming that compiling to an accde would accomplish that).

[hecon5]

In our environment, we have had to release compiled versions because any error causes Access to crash out entirely, and we also don't really want our users to be able to change code while running the installed files.

For green devs especially, when there's an issue with the Addin, and they're sent to the addin code (and not our application), they often haven't realized they're even looking at the Addin, and then send me upset messages when it turns out their code all got wiped when they changed it and closed.

This doesn't happen often, and for the most part, they all now know to check if they're troubleshooting our code or the addin.

Where I think it'd be REALLY nice is when we're working on the addin itself; because I cannot count the number of times I've been happily working and saving only to close and realized I'd been working on the installed addin, not the one I meant to work on, and then had to get up and get some coffee or my computer'd be used as a frisbee golf discuss into the sun.

Anyway, I am a huge proponent of open-source, but I do think it'd be nice to install as a compiled file, but provide all the code/regular version.