Alexander’s Blog

The following information is documented in Microsoft’s KB article 826993. The KB article also covers in details the steps related to InfoPath 2003 but I am only posting the portion that relates to InfoPath 2007.

In Microsoft Office InfoPath, you cannot submit form data to a Microsoft Windows SharePoint Services document library directly. This article describes how to design a form template that uses script to submit form data to a Windows SharePoint Services document library.

In InfoPath, you can submit the form data to a Windows SharePoint Services document library directly by using the UI. This article contains the steps that you have to use to do this.

Design your form data source and layout in InfoPath 2007
1. Start InfoPath 2007.
2. Click Design a Form Template, click Blank, and then click OK.
3. In the Design Tasks pane, click Data Source.
4. Right-click myFields, and then click Add.
5. In the Add Field or Group window, type FirstName as the name of the field, and then click OK.
6. In the Add Field or Group window, type MiddleInitial as the name of the field, and then click OK.
7. In the Add Field or Group window, type LastName as the name of the field, and then click OK.
8. Add the myFields group to the form, and then click Controls in Layout Table.

Submit the form data to a SharePoint Services document library
You can use script or the UI to submit the form data to the SharePoint Services document library.

Use the UI to submit the form data to a SharePoint Services document library in InfoPath 2007
1. On the Tools menu, click Submit Options. The Submit Options dialog box appears.
2. In the Submit Options dialog box, click Allow users to submit this form.
3. Click to select the Send form data to a single destination check box.
4. In the drop-down list, click SharePoint Document Library.
5. In the Submit Options dialog box, click Add. The Data Connection Wizard starts.
6. Type your SharePoint document library link in the Document Library box. Your document library link may resemble the following: http://ServerName/SiteName/DocumentLibraryName.
7. Type the document name in the File name box. You can use a document name such as TestForm.
8. Click Next.
9. In the Enter a name for this data connection box, type a name for this data connection.
10. In the Data Connection Wizard, click Finish.
11. In the Submit Options dialog box, click OK.
12. Save your form template as SubmitToWSS2007.xsn.

Test your form in InfoPath 2007
1. On the File menu, click Fill Out a Form. 
2. In the Fill Out a Form task pane, click SubmitToWSS2007. 
3. Complete the form.
4. On the File menu, click Submit. If the form is submitted successfully, you receive a message that indicates this.
5. Quit InfoPath. If you are prompted to save your changes to the form, click No.
6. Start Windows Internet Explorer. Locate your document form library. For example, your document form library may be http://ServerName/SiteName/DocumentLibraryName. A new item that is named testform is in the document library.
7. Click testform. The form that you submitted opens in InfoPath 2007.

Microsoft Office SharePoint Server 2007 (MOSS) supports Alternate Access Mapping (AAM) which allows the administrators to configure SharePoint so the users can access SharePoint sites using different URLs. The idea is to associate each Web application with a collection of mappings between internal and external URLs. For example, in certain situations, such as environments using reverse proxy or load balancing, the end user may type a different URL to access the site then the URL that is received by the Internet Information Services (IIS). In this situation, AAM will come handy and direct the user’s request to the proper URL.

You can also associate multiple internal URLs with a single public URL using one of 5 different authentication zones: Default, Intranet, Internet, Custom, and Extranet. Check out this TechNet articlefor more information on how to configure AAM in SharePoint.

Several years ago I was teaching a class at a local training center. One of my students, who worked for the Help Desk department at a large enterprise in Seattle, was blind. At the end of the week the student wanted to take the exam associated with the course. This required that a custom screen-reader software be installed on the computer where the exam was installed. We called Prometric who administers the exams for Microsoft. Prometric is a company that is well-known in the Microsoft Certified Trainer (MCT) community for their lousy service. So it was no surprise when they said they can’t really help because they don’t know what to do. Then we called Microsoft to see if they can help us accommodate the blind student so he could take the exam. Microsoft said we need to call Prometric because they are the ones who are responsible for the exams. We eventually ended up working a solution and the student was able to take the exam. The student missed the exam by only one question……ouch! That was very disappointing. But he was the only student bright and daring enough in that class to dare take the exam at the end of the week.

So when I read about this screen reader called WebAnywhere it caught my eye. I don’t know if it would help in the situation that I described above but it seems to be a great tool for the blinds to access the Web.

WebAnywhere is a Web-based screen reader for the Web developed by University of Washington computer science graduate Jeffrey Bigham. It requires no special software to be installed on the client machine and enables blind people to access the Web from any computer that has a sound card. Check out this link to go directly to WebAnywhere.

With WebAnywhere there is no need to purchase any software. Best of all, WebAnywhere will run on any machine, even heavily locked-down public terminals, regardless of what operating system it is running and regardless of what browsers are installed.

If you are looking into WebAnywhere, you might also be interested in this white paper.

A client of mine recently had the following issue. They had an HP ProLiant DL360 G5 server running Windows Server 2003 Enterprise edition. The server had 8GB of RAM but in the System Properties in Windows it displayed only 3.25GB of RAM. The CPU type and speed were displayed correctly and the BIOS showed the correct amount of RAM at boot.

You see memory below 4GB due to a limitation in the 32-bit operating systems. It is not specific to any brand (HP, Dell, etc.) The Physical Address Extension (PAE) is what can allow the operating system to address more than 4GB of memory. In Windows Server 2003, PAE is automatically enabled if the server is using hot-add memory devices. If you don’t have hot-add memory support then PAE is not automatically enabled and you would have to manually add the /PAE switch in the boot.ini file to take advantage of memory over 4GB.

The PAE switch needs to be added to all versions of 32-bit Windows that have more than 4GB of memory. The boot.ini should look like this.

[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(2)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(2)\WINDOWS=”Windows Server 2003, Enterprise” /fastdetect /PAE

When you reboot the computer after adding the /PAE switch, you will notice that the General tab of the System Properties lists Physical Address Extension at the end of the Computer section.

Note: On x86 systems, Windows Server 2003 Standard edition only supports up to 4GB of RAM but the Enterprise edition can support up to 32GB of RAM. Windows Server 2003 R2 Standard edition also supports up to 4GB of RAM but Windows Server 2003 Enterprise R2 edition supports up to 64GB. For more detailed system requirements check out this link on Microsoft TechNet’s Web site.

Have you noticed that when you use System Manager in Exchange Server 2003 to browse Mailboxes that the “Last logged on by” column frequently displays incorrect account information? For example, you may have noticed that your mailbox account shows other people listed in the “Last logged on by” column. This is often very confusing for the administrators. They are concerned about the security and finding several people being logged in to other people’s mailboxes is not very comforting. Rebooting the server won’t make a difference and even if your server is up to date with all the patches and hotfixes, the behavior still remains the same.

The reason for this “feature” displaying other users as “Last logged on by” in Exchange is that the other users are querying free/busy time. You can test this easily with a meeting entry and query someone else’s mailbox for free/busy time. You will notice that your name will show up in the “Last logged on by” column.