Your design goal here is not clear:
On the one hand, you imply you want to "automate" the process of inserting 200 "rows" in four steps. By "automate" I mean that the insertion will continue automatically without the user taking any direct action in the UI.
On the other hand, you imply the user should have some
control over whether to continue loading
after each step is complete.
If your goal is to load in four steps, but to
pause and notify the user that each step is finished successfully, that is a scenario where you are essentially giving the user a "status report:" why should the user be able to click a Button ?
But, if you want to give the user some
control after each loading step is complete: to continue ? to stop at the current step ? to start over ? Then, that's a scenario where you do want some kind of interface for the user to interact with.
There is a .NET method (WinForms, since FrameWork 1.1) for simulating a Click Event on a Button: [
^]. Except for automated testing of a UI in software development, I think using this method is not good software design: why not simply take whatever code is executed inside the Button and make it into a method which the Button calls, and which you can call as needed ?
While you could activate a Timer after each insertion step, and present a Button(s) that allowed the user to cancel, or re-start, etc., for a specific interval, I think that's generally a bad idea.