Access JumpStart 2.0 | Blog

A Rapid Development Framework for Microsoft Access

I didn’t make tons of progress on my Access AI setup yesterday and today other than I started to transition one project fully to Git, the Version Control System plugin, and utilizing cursor. I’m not too far in yet, but I set up a page on my internal Sharepoint site to record the steps I’m taking. A couple of little notes:

  1. When using the VCS plugin, I want to export the project and then import the project to make sure it’s working. This means I need to bypass my autoexec macro which sets up some things that don’t shut down nicely when VCS exports everything the first time. This also means I need to make sure I’m checking the local tables I use for app configuration and setup and make sure VCS is set up to export the data BEFORE I do my initial export. I’m not sure, but I think it was not exporting the data after the first export if I did not have it set to do so and if I hadn’t changed the table structure, but this might not have been an issue…
  2. After re-importing and testing, on some of my forms that referenced recordset fields with Me.[Field Name] the form would fail to compile saying that property or method was unavailable. I had run into this before and I know it’s an issue with the Access Import from text file function. I have to open the form in design view, select the recordsource and just hit enter and then save it. This will rebuild whatever internal Me structure that form has so it will then be able to see the recordset fields as properties and the form then builds.

I’m still learning Git and using TortoiseGit (I am using TortoiseSVN for my SVN shell). Since SVN and Git are both versioning systems there is some conceptual overlap, but there are a lot of differences in terminology. It was helpful to ask CoPilot to explain Git in terms an expert SVN user would understand. This helped me map some of the SVN concepts I was familiar with to Git.