InfoPath Dev

I am working with InfoPath 2003. The task at hand is this. We are scheduling meetings for multiple review dates. The solution requires that only 2 reviews can happen in any given day. I have been thinking that this should be no problem. Well, it is a problem… Here is why…
My data is in a repeating table. Each row represents the full data set for every review that is to be scheduled. There are 10 separate dates that must be scheduled on a regular cadence, again, no more than two meetings per designate review date available.

This is how I setup the supporting repeating tables. I figured that if I had a list of available dates, and a list of dates that have been taken, and then use an xpath filter to populate unique dates, which haven't been used by other review meetings.

Each pull down represents one of the review dates, and upon an insert operation, I add the selected date to the list of used dates.

The problem that I am having is that the pull downs are not filtering already used review dates.

i.e.
Repeating table 1 - scheduler
Pdown1
Pdown2
Pdown3

Repeating table 2 - available dates
Date filled rows

Repeating table 3 - used dates
Date filled rows


Another minor trouble that I am experiencing is deleting rows from the table 3, upon deletes. The code below deltes the data, but leaves the blank row.
I followed some instructions to use this for loop.
var objBlankRows = XDocument.DOM.selectNodes( "//my:ScheduledReview/my:Review-Date[.=\"\"]" ); //Enumerate through each of the rows we found for (i=0; i< objBlankRows.length -1; i++) { //Remove the row from its parent node debugger; objBlankRows.item(i).parentNode.removeChild( objBlankRows.item(i) ); }

If you can recommend some possible solutions, it would be greatly appreciated.

Hi TRubin and welcome to our forum!
Have you read the InfoPath blog post:http://blogs.msdn.com/infopath/archive/2006/08/10/694530.aspx
I think this may have some useful info for you. Please let me know if it doesn't, and we can help you do the right xpath.

Yes I did stumble across this, however; I didn't realize the blog was the answer to my question. The code that I have already written maintains the list of available dates, and the list of used dates. I found that I can use the xpath most widely published for drop downs, since the list of used dates is a seperate list.

For some quick testing, I created similar components to my solution, which are, master detail (main list), One repeating table for available dates, and a second for used dates. For testing I am manually populating both available, and used, dates.
To configure the pull down to get data, I set the pull down to filter data from the available dates. Then used the following filter, which filters things out that reside in field8, which is from the used date list.
not(. = xdXDocument:get-DOM()/my:myFields/my:group5/my:group6/my:field8)

This seems to function well on my test case. I will try this in my solution, the outcome seems likly to fumction as desired.

Thanks for the assistance.
Tim