InfoPath Dev

For my first post...

I have an InfoPath 2007 form that has undergone several Save As... updates. While testing the earlier versions I entered data in the fields, such as name, employee number, etc. and submitted the data to an email address and then after opening the attached form submitted (via a second view) to both Sharepoint Forms Library (after publishing) and a SQL Server database using submit rules in a button. No problem...got that to work. Btw, the "testing" environment was my own computer - I published the .xsn to a network location, launched it from there via a web address, filled it in via the InfoPath 2007 client, and submitted it. Then, as part of my first test of someone other than me using the form, the other person filled in the form on the main/default view and submitted it [via email to an email address]. The attached form was then opened from the email and on a another view a button was clicked to submit the form to Sharepoint Forms Library and SQL Server. This also worked fine. However, immediately after submitting the form data to the Forms Library and SQL Server, the data in the fields for name, employee number, etc. were changed to old values I had submitted weeks ago via an older version of the form! The person who submitted the attached form never had access to the previous test Sharepoint Forms Library and uses a different computer than me. It's almost like the .xsn had kept these old values within it somehow.

I searched for similar instances of this behavior, but couldn't find any. I read that for a different problem the solution was to clear the cache, so I decided to see if that would solve it. Assuming I cleared the cache properly (using infopath /cache clearall) via the command prompt, the problem still occurred.

Sequence:

1. Create form, publish to Sharepoint and network location
2. Test form on my own computer and on view #1 enter name=Barney Rubble and submit to email address
3. Open email address and open the attached form
4. On view #2, submit form data to Sharepoint and SQL Server
5. Edit form and use Save As
6. Publish to Sharepoint and network location
7. Test form on my own computer; On view #1 enter name=Wilma Flintstone; submit to email
8. Open attached form in email
9. On view #2, submit the form data to SP and SQL Server 
10. Edit form and use Save As
11. Publish to Sharepoint and network location
12. Repeat above steps a few more times...
13. Have someone else launch the form on his/her own computer and on view #1 fill it out using name=Fred Flintstone and submit to email
14. Open the attached form in the email on his/her own computer (same computer as in step 13)
15. On view #2, click button to submit to SP and SQL Server - the database is updated and SP has the form item
16. And then, while looking at view #2 on the form, the old data is displayed in the name field. I.e. Either Barney Rubble or Wilma Flintstone

Has anyone ever experienced this? Anyone got any idea what's going on?

Dan