InfoPath Dev

I've got three sharepoint lists defined that have one or more "Person or Group" type fields.

I'm working with Infopath 2007.  I have three combo boxes that list the contents of the three sharepoint lists.   When the user selects an option, I have a rule to copy the person's name from the sharepoint list, into a field in the infopath datasource.   The problem is that two of the lists will copy the names over as something like 250;#Doe, John  whereas the third will simply copy Doe, John.   I can deal with either scenario - but I can't deal with mixed results .  and I can't figure out why the one list is coming across different.  I compared the list settings and they are identical.

So as a simplified example, suppose one such list has:

 Store Number, Location, Dayshift Manager, Nightshift Manager
1000, New York, John Doe, Jane Doe

 In the infopath form you'd have a "Select Store" drop down.  When the user selects the store, a rule copies the dayshift manager into a field in the Infopath data source.

Any ideas?   The only thing I haven't done yet is blow away the list and recreate it .. I'd rather not do that if I don't have to .. that's a lot of data re-entry. 

Appreciate any suggestions.

Thanks

Generally, the syntax of {number};#Text means the column is a lookup. Is the column the same type in all your lists?

I'd probably put a rule on the field that is being set - that if the field itself (after being set) contains ";#", set it the substring after the # symbol. In a lot of cases, you can shoot yourself in the foot with this type of logic (what if there was a legitimate entry with those symbols in it?) but since you are pretty sure you have names here, and (I really hope) most names won't contain ";#", you'd likely be safe.

You were correct!  Thank you.

The actual field in question wasn't a lookup - but (using the example I provided) the store number was.    The list was recently migrated from Sharepoint 2007 - maybe something was affected there.

I deleted the column, recreated it as a text field and entered the values again - worked perfectly.

Thanks again.