InfoPath form printing issues

We received a requirement for an InfoPath form than need to be printed at the senders end and the receiving end.  We created the form and in testing it, we have discovered that any text that you type after scroll bars appear in a text field does not appear when you print the form.  Also, the text is not viewable in the email output from the form when it is received in the designated email account Inbox. 

The picture below contains two examples of such an issue:


I have had a look, and this is a limitation of the software as it is designed for electronic rather than printed forms. A potential way around this however is to amend your view “6a.Results”, so that instead of having a Text Box to show the result of the multiline boxes you use an Expression Box:


This allows you to pick a form field and shows it as free text that will expand vertically. There is however a known issue with this, and that is the fact that the output ignores carriage returns. I don’t know how this would affect the fields you are using it for; you could probably still use the multiline Text Box for fields such as address and use this for the more free-text fields such as the child details.

The other option of course is to make the multiline Text Box fields as tall as you think the biggest response will be, but that doesn’t look that great if only a small amount of information is entered into each box.


Lightning Conductor 2010 Express Web Part

Do you need a FREE roll up web part that also means you don’t have to spend money or time on developing XSL files to just display the correct columns? If so, download the Express version of our Lightning Conductor 2010 Web Part. It is not a trial, it is totally free:

Lightning Conductor 2010 Express Web Part

Making Outlook Calendar entries available through a SharePoint Calendar

A client asked me if it were possible to pool calendar entries from multiple Microsoft Outlook Calendar’s into one collaborated SharePoint calendar.  This is the best way I could think off, using SharePoint 2007 out of the box.  If there’s a better way to achieve this, please let me know.

Step 1: Create a Shared Calendar in Microsoft SharePoint

1. Click View All Site Content

2. Click Create

3. Select Calendar and follow the regular prompts

Step 1: Make a SharePoint Calendar available in Microsoft Outlook

1. Open a calendar on your SharePoint site.

2. On the Actions menu, click Connect to Outlook.


3. Confirm that you want to connect the SharePoint calendar to Outlook.


4. In Outlook 2007, you see both calendars side by side, and the calendar name has been added to the Other Calendars list. This side by side view is the default view.


Each calendar and the events that belong to it are color coded for easy identification. You can have multiple SharePoint calendars for different purposes and use the overlay view in Outlook 2007 to view any combination of those calendars by selecting them in the Other Calendars section in Outlook.

Step 2: How to Import Outlook Calendar items into SharePoint

1. With the source calendar open, go to view menu, current view, and select all appointments


2. Hit CTRL-A to select all the appointments, or just get the ones you want.

3. Drag-and-drop the selected local outlook calendar Items to the linked SharePoint calendar (found under SharePoint List on the left pane).


This is a two way process and can also be used to import SharePoint calendar items into Outlook.

Step 3: Invite other network users to share your SharePoint calendar

1. Right click over the SharePoint Calendar in Microsoft Outlook and click Share … Calendar


2. Send out email invitation


3. Complete the email with a recipient email address and click Send.

4. Once accepted other users with be able to view the SharePoint calendar


· When you view the SharePoint calendar within SharePoint, colour coding is not available to help users identify source of calendar entries. It is however available in Outlook.


· Some calendar events appear in the SharePoint calendar as copies. See snapshot above.

How to create a simple hyperlink from a css background image

I needed a way to hyperlink a background image placed in a SharePoint Master Page so it takes the visitor to the default home page.

The logo is embedded as a background image and want to be able to click-through back to the home page.  Currently the logo is being fed through the ms-globaltitlearea css:

        <td class="ms-globalTitleArea" valign="top">
                <table cellpadding="0" cellspacing="0" width="100%" border="0">

The solution is somewhat quick and dirty.  Create a transparent gif image and place this over the desired area, over the background image in your master page, then set the hyperlink to return the user to the home page.  Your code should look something like this:

<a href="/"><img src="/images/transparentlogo.gif" border="0"></a>

Therefore your final code will look something like this:

        <td class="ms-globalTitleArea" valign="top">
                <table cellpadding="0" cellspacing="0" width="100%" border="0">
                        <td style="width:350px;" rowspan="2">
                        <a href="/"><img src="/images/transparentlogo.gif" border="0"></a>

Telerik RADEditor Customisation

The RADEditor tools menu can be customised through the ‘toolsfile.xml’ file.  You can also populate the Fonts dropdown using the ToolsFile, as shown in the example below.  One thing to bear in mind though, any changes would be farm wide rather than web app specific.



    <module name="RadEditorDomInspector" dockingZone="Module" enabled="true" visible="true" />


  <tools name="MossTools1" dockable="false">

    <tool name="Cut" shortcut="CTRL+X" />

    <tool name="Copy" shortcut="CTRL+C" />

    <tool name="Paste" shortcut="CTRL+V" />

    <tool separator="true" />

    <tool name="Undo" shortcut="CTRL+Z" />

    <tool name="Redo" shortcut="CTRL+Y" />

    <tool separator="true" />

    <tool name="MOSSLinkManager" shortcut="CTRL+K" />

    <tool name="Unlink" shortcut="CTRL+SHIFT+K" />

    <tool name="ImageManager" shortcut="CTRL+G" />

    <tool name="MOSSTemplateManager" />

    <tool separator="true" />

    <tool name="MOSSInsertTable" />

    <tool name="SetTableProperties" />

    <tool name="ToggleTableBorder" />

    <tool separator="true" />

    <tool name="MOSSInsertTableElement" dropDownWidth="180">

      <tool name="InsertRowAbove" />

      <tool name="InsertRowBelow" />

      <tool name="InsertColumnLeft" />

      <tool name="InsertColumnRight" />

      <tool name="DeleteRow" />

      <tool name="DeleteColumn" />

      <tool name="SplitCell" />


    <tool name="MergeColumns" />

    <tool separator="true" />

    <tool name="ToggleSource" />

    <tool name="FormatStripper" />

    <tool separator="true" />

    <tool name="MOSSRightToLeft" />

    <tool name="MOSSLeftToRight" />

    <tool separator="true" />

    <tool name="MOSSHelp" />


  <tools name="MossTools2" dockable="false">

    <tool name="ApplyClass" />

    <tool name="FormatBlock" />

    <tool separator="true" />

    <tool name="FontName" />

    <tool name="FontSize" />

    <tool separator="true" />

    <tool name="Bold" shortcut="CTRL+B" />

    <tool name="Italic" shortcut="CTRL+I" />

    <tool name="Underline" shortcut="CTRL+U" />

    <tool separator="true" />

    <tool name="JustifyLeft" />

    <tool name="JustifyCenter" />

    <tool name="JustifyRight" />

    <tool separator="true" />

    <tool name="InsertOrderedList" />

    <tool name="InsertUnorderedList" />

    <tool separator="true" />

    <tool name="Indent" />

    <tool name="Outdent" />

    <tool separator="true" />

    <tool name="ForeColor" />

    <tool name="BackColor" />



  <item name="Arial" />

  <item name="Calibri" />



    <contextMenu forElement="*">

      <tool name="Cut"/>

      <tool name="Copy"/>

      <tool name="Paste"/>




SharePoint Content Deployment – System Out of Memory Exception messages

We run Central Admin content deployment jobs continually.  A couple of days ago, every job we have started to fail with memory management errors occuring on the target machine: System.OutofMemoryException etc. 

A search of the Internet turned up a few interesting blogs.  The solution seems to be rather trivial: reboot your systems regularly.