That looks simple enough. Of course, I have to multiply this by 9 for the number of sets tables to be managed and wrap the entire thing in one or more transactions but it looks doable. The only issue, and it’s always an issue, is error handling in a batch process. I notice the return from the insert is Boolean. Does the entire process have to fail if one or more inserts fail? I’d like to capture the failures and either correct them for next time or move them manually or, at least report them. How could this be done?

Your second code fragment using #Loadable is quite similar to what I do now. I probably shouldn’t admit this because it’s so very… well, FoxPro, but the process as currently written uses remote views to append the data to history. It’s easy to identify and process any failed updates. But, remote views lack the pizzazz and credibility of SPT and SPs. That’s why I’m trying to re-write the process.