You can use your favorite social network to register or link an existing account:
Or use your email address to register without a social network:
Sign in with these social networks:
Or enter your username and password
Forgot your password?
Yes, please link my existing account with for quick, secure access.
No, I would like to create a new account with my profile information.
We'll walk through 2 scenarios in this post - one for collecting new data with an HTML form, the other for updating existing data with an InfoPath form. Data collection works on tables and queries, so the first step is to select a table or query from the Nav Pane. You can either right-click on the object and select "Collect and Update Data via E-mail"
or you can click on "Create Email" under the "Collect Data" chunk of the "External Data" tab in the ribbon UI.
(Click image to enlarge)
That launches a wizard to create and send the email. The first step of the wizard describes the process:
Next, you choose whether to send InfoPath or HTML mail. InfoPath provides a rich experience with dropdown controls, in-form validation, and so on. Although HTML pages can contain these things, HTML mail cannot as they're blocked by most firewalls and email gateways. As a result, HTML forms are simple edit controls. In this case, we'll choose HTML:
The next step is to choose which fields to include in the emailed form:
Then you choose what happens to the mails when they come back. You can either have the replies processed automatically or manually do it yourself:
If you choose to process replies automatically, you can set the following options to govern how that automatic processing works by clicking on the "Set properties..." link on the wizard dialog.
Next, you have to tell Access who to send the forms to. You can either use a link to a table of email addresses or you can simply type a list of names into the email header:
The next to the last step is to create a subject line for the email and (optionally) type an introduction that goes in the top of the email, above the form:
Finally, you can hit the "Create" button and we'll create the email message, and it is ready to send - all you need to do is hit "Send" in the Outlook send note:
The final email message will look something like this:
The process for creating a mail to update a table with a form sent through InfoPath is quite similar. If the table or query you select in the first step has any data in it, you'll be asked if you'd like to simply collect new information or update the existing information (this pane of the wizard didn't show in the example above because the table was empty). Users who are asked to update information can also add new records at the same time. In this case, we'll update the existing information:
When automatically processing replies for data updates, you can control what happens to additional records (either automatically adding or discarding them).
In this example, we'll use a list of email names in the database rather than manually typing them into the Outlook mail note:
Just as before, you can set the email header and introduction. In addition, you can choose where the addresses are attached to the mail (e.g. so you can set them to the BCC line and prevent everyone from seeing them).
Since the email that is sent will contain data (rather than simply a form), there's a warning that you're sending out potentially confidential or sensitive data, and to verify what you're doing.
The last page of the wizard shows each of the email recipients, and allows you to verify that you're mailing the right list. This allows you to make sure that the mails go to the right people, since you're pulling the addresses from a table rather than manually typing them in as you did in the previous example.
The final InfoPath email is a rich form that users can update directly from the Outlook email reply note.
In the next post, I'll show what happens when the replies come back.
This looks really, really good. Using HTML for basic data gathering is good, but the Infopath forms look excellent. Is Microsoft going to release an Infopath "runtime" for people who want to use Infopath forms for such Access-based data collection? I see that various people and companies are trying to do such things and it seems strange that Microsoft have not filled this hole themselves (if I have understood this correctly of course).
Sounds really great! Please tell us a bit about adding code behind the controls of HTML vs InforPath forms. Does either type of form support any kind of event model (for validatation, etc) ?
This feature is no doubt one of the best new features of Access. However, Microsoft Outlook security prevents HTML mail in many organizations. Is there an option to return text responses?
Is there any way to convert Access forms to HTML or InfoPath for data collection? If so, what about code or macros in the form?
>> Is Microsoft going to release an Infopath "runtime" for people >> who want to use Infopath forms for such Access-based data collection? There has been discussion about an InfoPath runtime but we don't have anything to announce on that topic. >> Please tell us a bit about adding code behind the controls of >> HTML vs InfoPath forms. Does either type of form support >> any kind of event model (for validatation, etc) ? Field and table level validations are enforced when the data is actually added to the records. You likely won't ever get clientside validation for HTML forms as all popular email clients block script. InfoPath forms will require users to enter required fields but not field and table validations in the browser message. We will be writing a white paper about how you can create custom InfoPath forms that could have client-side validation rules. >> Is there an option to return text responses? Not at this time--something we want to consider for the vnext. >> Is there any way to convert Access forms to HTML or InfoPath for data collection? Not at this time--something we want to consider for the vnext.
I am already contemplating application of this new feature. I can't count the number of systems I've built already that could have used this feature. (Systems that email invitations to take a survey with a link to a webpage are ok, but this solution is great.) If I stay in the consulting world, this will definately be an added plus. These questions may be answered in the next post, but if not, I'll ask them now: Is the email adress of the responder going to be a capturable field?
This may be offpoint, but will Access 2007 still work with DAO? I am trying to install MS Note 209891 "How to fill a treeview control recursively in Access 2000." If you remember, this is a hierarchy of Northwind employees reporting relationships based on the field "ReportsTo". I have no problem placing the Microsoft Treeview control 6.0 (SP6) control on my form. The note says that Microsoft DAO 3.6 Object Library must be available, and when I go to my form's code for References and check the DAO 3.6 Object library line and then [OK], the following error message results: Name conflict with existing module, project, or object library. Does anyone know if this is by design, a bug, or whether a workaround exists. Note that this note is an update of Access 97 note 167309. If MS has changed the rules, it sure would be nice for them to publish a note update for Access 2007. Bob
I have just determined by experimentation that the following objects have a conflict and may not be used together: Microsoft Office 2007 Access DB engine objects
Microsoft DAO 3.6 Object library. Does anyone have some sample code of how to fill a treeview control without using DAO? Thanks, Bob
YIKES! quote: <I have just determined by experimentation that the following objects have a conflict and may not be used together: Microsoft Office 2007 Access DB engine objects Microsoft DAO 3.6 Object library. I say again - YIKES! Is it true that DAO cannot be used in 2007??? This would mean serious retooling of many, many deployed apps... BC
Bob, there is no need to use the "Microsoft Office 2007 Access DB engine objects" and the "Microsoft DAO 3.6 Object" library together because they are mutually exclusive. The "Microsoft Office 2007 Access DB engine objects" are a complete superset of DAO 3.6. None of your existing code needs to change in order to use the new Access database engine objects. All of your existing code will run unmodified. The code to fill a TreeView Control with data is the same regardless of whether you are using DAO or the new Access database engine objects.
When receiving replies to my form, messages are not processed by outlook, i.e. they are not sent in the folder defined by the wizard and I don't see "Export data in Microsoft office access" when I right clik on the reply. Addin for data collection in outlook is enabled.
I was keen to see if Pocket Outlook (WM 5.0) would be able to handle these email forms - unfortunately it appears not. Is there an add-in that could allow/enable this as filling out these forms on a pda would be extremely useful.
Hello, nice site look this:
http://boots.paritsa.info boot [url=http://boots.paritsa.info]boot[/url] End ^) See you
Nice site guys.. didnt have a chance to meet you guys at the conference but hope to see you guys in bing in the near future. stay up.
Carisoprodol is best pain killer! Buy it! haygoodlab.ucsd.edu/.../404.html