InfoPath Dev

Hello, I've created a simple address book form that I've published on SharePoint. Everything's working okay so far, but I've encountered a problem: when I edit and submit an existing contact in the address book form, the contact is not updated but instead a new contact is added to the form library. I currently using a formula to generate the contact filename ("Contact - [FirstName] [LastName].xml"). What's the best solution to edit a contact without creating a new contact entry? Thanks, Tom

What is the name of the new contact file?

You may need to look at the document library settings and see if overwrite is enabled.

A new contact is created only if you change the first or last name on an existing contact because of the file naming rule I mentioned before. However, I was hoping InfoPath would be smart enough to know that I'm modifying the existing contact, so if I change a contact from John Doe to Johnny Doe, it should *rename* the contact filename to "Contact - Johnny Doe.xml" instead of adding a new contact to the list.

Basically, I'm trying to emulate something like Yahoo! Address Book (when you edit your Yahoo! contact's name and hit 'Save', it edits the current contact you're editing instead of adding a new contact). Tom P.S. Yes, overwrite is currently enabled.

Ok I gotcha.

You could change your file naming to a numeric and then promote the name fields, etc. This way the file (link) could remain the same and you would see the latest information in the additional columns of the Library.

Or you should look at deleting items from a library via a caml.  You could add functionality to your form where if it was a name change it would delete the previous form so there was still just one.

Actually the best implementation I have seen is to put your contacts in a database and then have one form that can browse the contacts, lookups, search, etc.

Hi Clay, Thanks for your help. I've never heard of CAML before, so I'll go read up on it. I think for the time being I'm going to change the file naming rule to an incrementing number. Unfortunately my contraint is that I don't have access to a database -- I can only publish to SharePoint. Tom