@Erika_K Thank you for your response. That was quite a bit of information.
Luckily, all users are now logged in as they should be. I think this was due to a Verify and Rebuild, as I did nothing else and they all connected.
The remaining issue is much more sticky. As of now, I have:
1. A 'main' company file that all but one user has been updating.
2. A 'rogue' company file, separate from the main above, that one user kept using after it was accessed by me in a QB support session, trying to get the first/initial login issue fixed.
note: My first knowledge of this was when on 10/24 the lone user and a user of the main file said they could not see each other's transactions.
The second file has only this user's transactions in it for 10/23 and 10/24. Before that, as it was a backup, it should be easy to determine if inspected. This 'rogue' file is saved in a directory with it's associated meta files, inaccessible to all users.
The main file has all other user activity throughout this period.
Objective: Somehow (copy/paste, export/import, backup/restore, ?) get the rogue company file's activity (virtually all sales/invoices) into the main company file.
Although I have wrestled with QB for several years with a variety of versions and customers, this issue is foreign to me, and I have found no direct solutions in my topical search. I do know that a simple 'merge' is not only impossible, but if it were, it would be a disaster.
But the product has been around a while now, and I can't be the first to be in this pickle. I'm hoping there is a way to do this, especially since the 'missing' data is so clearly identifiable in it's own company file. What is simple to say likely means it will not be simple to do!
Again, many thanks to you for a thorough, non-boilerplate reply.
