warned Phil

Phil reported, a couple of days ago, a problem with the new import process for the RASC membership data. Despite selecting a subset, all the new candidates were imported. I was intrigued. Today, finally, we sat down, briefly, and tried the process—with the latest December data.

He had completed the first couple of steps. Then, as I watched, he checked off the (truly) new people. And then he switched to the form to initiate the next step of the procedure. I stopped him. "Close the open query." As I said it, I recalled thinking about this when I had developed the code. "Oh," Phil said, "I didn't do that before." I explained there'd be conflicts. It worked fine this time.

Good. But a slight error on my part for not documenting or warning of this requirement.