InfoPath Dev

I'd like to prevent users from removing rows from a repeating table as well as change the text of the "Insert Before/After" commands. It's my understanding that these can be accomplished via the "Customize Commands..."
button, but it's disabled on the "Data" tab of the "Repeating Table
Properties" dialogue.
Note that I'm using InfoPath 2007 and a Web Service as the Main data source -- and the repeating table control in question is bound to this Main data source.

Thanks in advance!

- Hersh

Normally I would tell you it is because you are using a secondary data source... but in your case it is the main data source.

Now, I have not tested this, but it could be because your main data source is "really" a secondary data source (i.e. a Web service)...

You should be able to tell whether this is the case by designing 2 new blank forms... one with an InfoPath developed data source, and one with a data source bound to a Web service. Don't do anything more than that with these 2 forms... then place a repeating table into the view of each, and check if "Customize Commands" is disabled. My guess is that it is because of using what is typically a secondary data source as the main data source.

Greg, Thanks (again) for your reply. I tried your experiment and it indeed shows that when using an InfoPath developed data source, the "Customize Commands..." button is NOT disabled, but when using a Web Service as the data source it IS disabled.
I don't know why this is, but I discovered a work-around to prevent users from removing rows from the repeating table, which is to manually adjust the manifest.xsf file. In my case it involved commenting out the following line in this file:

<xsf:button action="xCollection::remove" xmlToEdit="Benchmark_7" caption="Remove Benchmark" showIf="immediate"></xsf:button>

This solution is less than ideal because the xsf file gets updated each time the template is updated via InfoPath. But it works.

I'm sorry to hear the issue. I don't know of any workaround. I did reply to another thread of yours (not sure it was here or on the MS Newsgroups) that you might try modifying the showIf value to see if you can get around it that way. I have low expectations that that would do any good... but you never know.