Vlad:
Good morning -- thank you for the follow-up... so, now I'm a bit confused now. Allow me to recap:
1. The version from ~ a week ago, resulted in numerous VBA errors (incl. -- if I recall correctly -- a 3371 error).
2. Based on the mapping at that point, I considered them "scenario 1" and "scenario 2" errors.
2a. Scenario 1 error: There were duplicate AFSAS fieldnames within the *same product* AND *same source (organization)*
2b. Scenario 2 error: There were duplicate AFSAS fieldnames within the *same product* but in different sources/organizations.
3. Per 2b., the scenario 2 errors were fixed first by including the SOURCE_FILE as an additional criteria.
4. Next, any dups due to scenario 1 were *temporarily* removed (for testing only). At that point, the code executed and all products were created as expected.
5. It then took me some time to review all mapping issues due to scenario 1 errors. Once remapped, all previously removed/deleted records were added again. At that point, the code executed and all products were created.
5b. See attached JPG reflecting that there are no dups in the project_tables regardless of scenario 1 or scenario 2.
All that said, prior to opening the yesterday's new post, the VBA executed and all products were created as expected. So, this is why I'm a bit confused now. The introduction of the new code now prevents the same outcome. Is it possible that something (e.g., including "source" to prevent scenario 2 errors) was left out in the added code? Otherwise, why was it working (w/ the same mapping) yesterday but it is no longer working now?
What am I overlooking in this scenario?
Thank you,
Tom