While the answer is yes, you might ask a lot more questions such as how and so on. For years folk have been distributing apps and work across computers so there's nothing stopping you but you.
But there's a glaring issue in that 1 line of code. The data source looks "hard coded" to a specific user and database. While it may run on that user account on many machines, why is it that hard coded?
Which is exactly why I pointed out the issue with that hardcoded path to the database.
Now that you asked or told about more than one user working on the same data my head exploded. I've seen so many Access and many user failures over the years that over a decade ago I dropped Access and started using MySQL for the database and at first VB6 for front ends. Today I use MySQL for the database and server and C# for the frontends.
I suggest you kick up your game many notches and move to SQL ASAP.
As you can see my brother I have already used sql tables and Visual basic and I want to explain how to run the final program on each network internal pcs and the work of several users on the same tables, even a simple explanation
Thank you for your cooperation