Well, I powered through this. I opened the exported file in Excel; it had 10317 lines.
Then, in Sesame, I sorted my imported records by code (it's my customer file), and got the code number to match up to the line number. Then I just had to keep moving down the screen, watching for mismatches, and recording the missing numbers (essentially exactly as Bob suggested, though I hadn't seen his suggestion yet). Each time, I checked the Q&A file to see if the missing records had any sort of weirdness to them, but nothing jumped out at me. Eventually I got through all 10302 Sesame records and had a list of missing Q&A records.
Then, back to Q&A. I exported those records, and imported them into Sesame. Sesame accepted them all. I now have a matching count in both programs.
But no idea why they were missed in the first pass. I hope it doesn't happen when I export/import my invoices and workorders, because there's far more than 10,000 or each of those (approximately 3 times as many in each database, and I already know that there are missing numbers in each of them. I've been scrupulous about keeping Customer clean, with no skipped codes, but it hasn't been a concern with Invoice or Workorder.)
Perhaps it's related to the record loss issue that Spencer brought to light? I have not yet upgraded everything to 2.0.2, but I will before importing my Invoices and Workorders.
In any case, Customer.db is happy and full. Time for a coffee break. Thanks for the advice, Bob and Erika.
|