I have learned from past experience that it can be hazardous to make changes to a back-end data table when it is bound to an existing VB.NET project in Visual Studio.
I would like to believe that it is possible to pull this task off without crashing my project, and would like to seek any advise from the EE community on how to do this.
Specifically, I have a single MDB file which contains a dozen or so tables and queries/views, with all their relationships. Everything is created/designed using MS Access 2016.
I want to change the primary key on one of the tables within that MDB. That would also require removing some of the relationships, and establishing new ones as needed.
Right now, the primary key for the Roster table is sequentially assigned, but the first non-primary field is and always will be unique, so I would really like to change it.
So, I am looking for some step-by-step instructions from someone who has successfully done this within the context of a previously bound Visual Studio project.
As always, don't hesitate to ask if I've left any important details out.