Originally Posted by Cronk
This to me sounds like you have not split your database ie tables,queries,forms etc are all in the one database file and you only want to export the data.
Why not split the data tables into a back end file and send that accdb file to other users.
Your response above seems to imply several users are adding/editing data. How are you going to synchronize changes?
The database is split into back-end and front-end. The feature request from the users was specifically that they want to have the ability to back up and restore using XML files.
The users have no need to merge data; each person is going to have their own records. I can't get into much detail, but you can think of it like this; each user's version of this software is going to contain their own personal notes on a particular item. This is meaningful to share between users once in a while, but having everyone on one back-end would muddy the waters.
I was able to implement a solution, fully functional. I had to do things the hard way: test each table as it was imported for dependency complaints. When there was a complaint, rearrange the import procedure to import that particular table later and test again. I hate hard-coding all those tables like that, but when there's dependency constraints and it has to be done in a specific order...¯\_(ツ)_/¯