About two months ago I had a serious corruption that none of the basic solutions would solve. I resorted to importing tables 1 by 1 into a new database. That worked however I lost all my relationships; it was very painful because I have quite a few and working in the Access visual tool is painful. ChatGPT and I spent about a month getting relationship subroutines and a backup program for back-end data files working. It took many iterations to get it right, at least to my satisfaction.

ChatGPT likes to do things its way, which often isn't correct and it took a lot of coercing and dozens of iterations to finally come up with something that's stable and reliable. I tailored them to my database designs so the overall concept would work for anybody, but not the specifics (unless you're using the ADS). I suggest all developers make that duplicate effort for themselves and their clients for when that corruption will occur.