Repair Oversized Access Split Database

My Access split database has grown past the 2 GB limit; once that happened it slowed to a crawl and, after I moved the file to another location on our network, the back-end now refuses to open at all—Access 2024 simply reports “Not a valid path.” I’ve already tried re-linking the tables, running Compact & Repair, and restoring from backup, but none of those attempts brought it back. The front-end is still on the same network share. Here’s what I need: • Recover the back-end so it opens normally. • Reduce the file size or otherwise restructure the data so we stay safely under 2 GB. • Re-link the front-end and confirm forms, queries, and reports run at normal speed over the network. • Provide a concise summary of the steps taken so I can maintain the solution. I can supply the front-end file, the problem back-end, and remote access to the network share. If you think migrating tables to SQL Server Express, archiving old data, or another approach would be cleaner, I’m open to your recommendations. Let me know how long you’ll need and which tools you prefer (VBA, Jet Compact Utility, ACE OLEDB, etc.). I’m eager to get this database stable and responsive again as soon as possible.

Project ID: 40372452