OpenArgs (my) class way (1 Viewer)

[OT: "npm" for Access]

The same would also be useful for add-ins etc.
Ideas have already been introduced in prominent place (Access DevCon 2023):

If there were a "catalog" of these code modules, an add-in could be developed with a manageable amount of effort. (I already use an add-in for importing code modules including their dependencies, which could be expanded or parts of it could be used).
Since I also consider this to be useful, I would be happy to discuss ideas/conceptions about such an add-in + catalog in more detail.
However, I suggest an extra thread for this so that John's thread is not totally hijacked. :)
LOL, too late! :D
 
I suggest an extra thread for this so that John's thread is not totally hijacked. :)
Yes, that’s exactly what I was referring to. Being able to find and mindlessly integrate stuff without a paywall and with an active community of people improving it and keeping it alive would definitely bring some life to this.

@Josef P.
I would share some time for that thread, if you're willing to maintain it. Hopefully others do too.
 
If there were a "catalog" of these code modules,

Using Access’s File Insert with a GitHub Code Repository

Microsoft Access’s Visual Basic Editor (VBE) includes a handy **Insert > File** feature, allowing you to insert the contents of a text file (e.g., `.txt` or `.bas`) directly into a VBA module during editing.

This is perfect for reusing code snippets or templates stored locally. To enhance this, you can link the local folder to a **GitHub repository**, creating a centralized, online repository of code samples accessible to your team or community.

By cloning the repository to a local folder (via `git clone`) and keeping it synced with `git pull`, you can browse and insert the latest code samples using Access’s built-in feature.

For inspiration, the **msaccess-vcs-addin** project by joyfullservice on GitHub (https://github.com/joyfullservice/msaccess-vcs-addin) uses a similar concept for version control, exporting Access objects as text files and recommending UTF-8 encoding for compatibility with Git.

This approach combines Access’s simplicity with GitHub’s collaborative power, streamlining code reuse.
 

Users who are viewing this thread

Back
Top Bottom