>>>Definitely Doug! I know it can increase the indexing time but indexing a 2 million records table is a process that takes already a long time and because I don't show the progression, the user presses the button a second time anyway!
>>>
>>
>>Once the user clicks the button to start indexing, disable the button before the indexing starts.
>
>Not sure it will work each time - I had such a thing with a Save button which did some lengthy processing, and I actually had to place a transparent shape over it, to eat the extra clicks. Disabled button seemed to still accumulate clicks, so I called its click from the shape's click, if it was enabled. It solved the extra clicks problem.

Hi,

When I disable a command button I put a transparent shape on top of it. Later, when I enable the command button I change ZOrder and put button on the top. So no need to have code in shape's click event.