Your development environment is important. You want to have fast performance as you develop and you want it to remain stable so it doesn’t crash.

I have a decent desktop with 2TB of NVME storage (the fastest I could get when I built it), two monitors and 64GB of memory.

I run both Access and SQL Server on the machine and also made sure I had similar specs for my laptop.

For me, I want a development environment which will not slow me down, but give me plenty of room and space and speed.

On the other hand, I also want to know how the system is going to perform on my client’s network. I typically work with my clients and so far have been able to get VPN and remote access to my customers system with a licensed copy of Access.

This allows me to create development versions just for me where I can test and make sure the performance of the system is going to be acceptable before I give the users a release. Sometimes, that blazing local piped connection to your SQL Server on the same system you are testing the Access program on blazes, but all of a sudden, with a LAN based SQL Server on the client network, or an Azure server in the cloud two states away brings your beloved code to a crawl. In times like these, you need to be doing this BEFORE you are showing the client or DEPLOYING the app.

That way you can begin to address the problem right away!

Do you have a good pipeline for testing deployments in your customers environment before deploying?