Search results

A basic requirement for me would be that the code is provided as a text file and not within an accdb. Whether it is then available in just one or in multiple repositories doesn’t really matter to me. I am currently thinking more in the direction of a catalog that enables automated import from...

Vision: .. and later create an add-in with AI support to find the required code modules ;)

I see a 'catalog' on GitHub more machine-readable. Perhaps one JSON file or similar for each repository. It might even be possible to create HTML pages directly via a workflow. The main effort of a “catalog” will be in maintenance and updating. Therefore, GitHub could be a useful platform if...

Found on GitHub: https://github.com/sancarn/awesome-vba/

I already do that. ;) But these are just my code modules. My GitHub repository for VBA code: https://github.com/AccessCodeLib/AccessCodeLib A catalog of several repositories with such code modules would be interesting.

Inspired by some recent forum posts and the ideas mentioned at Access DevCon 2023, I’d like to open a dedicated thread to discuss the concept of a shared catalog of reusable code modules and add-ins for Microsoft Access / VBA. Let’s gather here what already exists (tools, code collections...

I already do that. ;) New Thread: https://www.access-programmers.co.uk/forums/threads/code-catalog-for-access-vba-making-code-sharing-easy.334177/

Briefly explained with sample code to be on the safe side: Dim SearchBoxStringInsertedByUser as String SearchBoxStringInsertedByUser = "abc" Debug.Print "User insered: "; SearchBoxStringInsertedByUser Dim strSQL As String strSQL = "[TransDesc] = '*" & SearchBoxStringInsertedByUser & "*'"...

.. and now test this: write in Me.SearchBox: ' or 'a' like ' ;) => to avoid sql injection use: strSQL = "[TransDesc] Like '*" & replace(Me.SearchBox, "'", "''") & "*'"

[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...

"Access DevOps/CI" is running :) Example: Feature request or fix bug => (Work process is reduced to the essentials) Earlier practice: create branch if possible: write tests for it implement feature/bugfix - TDD (run specific tests locally) export (msaccess-vcs) + run all unit tests (call by...

If anyone wants to test the Powershell scripts: attached is a zip file with the scripts and the sources of a test application. The call of the build script looks like this, for example: .\Build.ps1 -SourceDir "source" -Compile $true -AppConfigFile ".\Application-Config.json"

Done. :) Skripts repository (for GitHub and Azure devops): https://github.com/AccessCodeLib/msaccess-vcs-build Examples of usage: Github workflow: https://github.com/AccessCodeLib/BuildAccdeExample/blob/main/.github/workflows/Build-self-hosted-O64.yml Azure devops pipeline...

Concept for setting properties: Powershell script: https://github.com/AccessCodeLib/msaccess-vcs-build/blob/main/scripts/Prepare-Application.ps1 Config file (json): https://github.com/AccessCodeLib/msaccess-vcs-build/blob/main/examples/Prepare-Application-Config.json Note: json is very easy to...

Here's a little puzzle I didn't solve immediately. Task: Execute SysCmd 603 (acSysCmdCompile) in Powershell. Code: param( [string]$SourceFile ) $accdbPath = $SourceFile #append current path if SourceFile is not full path: if (-not ([System.IO.Path]::IsPathRooted($accdbPath))) {...

Yes, I plan to do that, as I use Azure devops for my customer projects. For Azure devops I also need the 2 runners for the 32- and 64-bit accde files. Powershell can also be used in Azure pipelines. That's why I use this as the main control and only call the script via the GitHub action. The...

Then I'll continue talking to myself and announce a few interim results. :) Build scripts are ready: https://github.com/AccessCodeLib/msaccess-vcs-build Note: The Powershell scripts can also be executed locally without a YAML file for a workflow. Example GitHub workflow...

https://docs.github.com/en/actions/hosting-your-own-runners/managing-self-hosted-runners/about-self-hosted-runners This allows you to use your own server / VM as a runner for the GitHub workflow.

Note: Result of my experiments: a self-hosted runner currently seems to be the best option. 1x runner with installed Office 64 bit 1x runner with installed Office 32 bit This eliminates the long installation time and I feel more comfortable with the license because I can use my own license and...

Does anyone have experience in automating the creation of an accde via GitHub/Azure devops workflows? A workflow to create an accdb from the source files created with msaccess-vcs already works. My plan: install Office 64 bit create accdb from the source (optional) run tests (64 bit) create...