-
- You have to build the DB in SQL first
- Create a web service to interact with it (read/write)
- Create a new, blank form that is browser-enabled and create data connections for submit and receive using your web service(s)
- Convert the data connections to UDC, which saves them in a Data Connection Library (MOSS only)
- Create a Single ...
-
Show All Items just means no filter is being applied. The Item Limit is always in play, though.
-
Default receive data connections from SharePoint only show whatever is in your default view. OOTB, the default view of a list has an Item Limit of 100, so it is not surprising that you're only seeing a subset. 50 would only make sense if the item limit has been lowered to 50 or if your default view has a filter that only shows ...
-
Just modify your view(s) and don't show those columns.
-
Using username will not be unique, because the same user may submit more than one form.. Timestamp is much better using the now() function. I actually use userName() combined with now():
concat(userName(),"-",now())
-
People don't typically buy NEW licenses each time, so that doesn't matter. Organizations typically have an enterprise agreement that covers all the Office licenses for each user, and they can move up to the next version no problem. It is extremely unlikely for them to jump 2 versions of Office.
-
I just tested it with one of my forms, and it created/opened the PDF just fine. Specs:
- Win7 64-bit
- Adobe Reader 9
- Office 2010 but it was an InfoPath 2007 form
Haven't ever had an issue with it on the work computer either, which is WinXP 32-bit w/Office 2007 and Adobe Reader 9.
-
Doesn't have to be a test site. Can be a different library on the same site. Simply put, if you publish a new template, then it overwrites the template in that form library and therefore must show changes. You can't be publishing a form without seeing changes unless maybe you have it set not to upgrade automatically, but ...
-
Isn't the form originating from a form library? Each time you submit the form, it should also be submitting to a form library for subsequent usage. You wouldn't just submit it to the DB. I am not sure how your form isn't already in a form library unless you arne't using SharePoint at all and have it published to a ...
-
If you have any InfoPath 2010 questions (including SharePoint-related InfoPath questions), feel free to ask them here or in your own thread. I look forward to them...