I’m failing at blogging big time at the moment. I’ve had several ideas for posts recently but I seem to start them and can’t finish them.

Anyway, this one seemed to write itself so hopefully it’ll be a bit of a kick start!

I took a call earlier in the week as someone wanted to print on both sides of the page while using Word 2010.

This is what she was expecting to see in the print options.

As you can see there are options to flip on either the long edge or the short edge.

This is what she was seeing instead.

My first thought was that the duplex option hadn’t been enabled on the printer driver but this wasn’t the case. Clicking through to the printer properties allowed the user to choose double sided printing which came out as expected.

I’d like to say I could take the credit for figuring this out but a search helped me out.

I found this thread on a Microsoft support forum which detailed the same problem.

It suggested the cause was down to a missing DLL

c:\windows\system32\prntvpt.dll

It was indeed not the system.

I upgraded the .NET framework on the PC to version 4 but this still didn’t solve the problem

The thread suggested two other options,

1) Uninstall .Net Framework and reinstall.

2) Copy the dll from another PC.

I went for option 2.

I found a PC that was on the same .NET version, copied the DLL and ran the following from a command prompt

REGSVR32 c:\windows\system32\prntvpt.dll

I reopened Word 2010 and the double sided options reappeared.

This was a Windows XP system but I’m pretty sure the same thing would apply for Vista/Windows 7.

Just a quick one as a reminder as it caught me out!

You’re probably aware that Outlook stores the names that appear when you type a mail recipient in an .NK2 file.

In the past when moving a user between PCs all we needed to do with grab the .NK2 file from the old PC and copy it to the new PC.

Turns out Outlook 2010 doesn’t use an NK2 file anymore!

If you’re using Outlook 2010 look at your contacts folders. You should see a folder called “Suggested Contacts”

This where the names are now stored.

The idea is that you can easily manage them and more importantly because the names are stored in your mailbox they will follow you around on different PCs.

So the main thing is how do you transfer them across from an old PC running an older version of Outlook?

There is a Microsoft Knowledgebase article detailing the whole thing here.

Simply put,

Outlook has a command line flag “/importNK2”.

Grab the NK2 file on the old PC from one of the following locations.

• Windows XP
  Drive:\Documents and Settings\Username\Application Data\Microsoft\Outlook
• Windows Vista and later versions
  Drive:\Users\Username\AppData\Roaming\Microsoft\Outlook

Browse to the folder “%appdata%\Microsoft\Outlook”

Make sure the NK2 file is in that folder and the filename matches your Outlook profile name.

e.g Andy.NK2

Run Outlook with the switc

Outlook.exe /importNK2

Done!

The KB article says that the import process renames the file with a .file extension but this didn’t seem to happen when I did it. (though it might have just been me!)

Note if you perform an upgrade from an old version of Outlook to Outlook 2010 this should have been done for you automatically

Yeah i know….me again.

We’ve had a speaker drop out at short notice so I’m going to speaking at AMITPRO this month. The topic is one you’ll probably know is something I quite like talking about – SharePoint!

My presentation will be titled – SharePoint as a Helpdesk

I’ve had the idea for the while so it’s something Guy and I have been sort of keeping in reserve just in case we had any issues with speakers so I finally get to roll it out this month.

So what exactly do I mean by SharePoint as a Helpdesk?

One thing I’ve found when talking to other partners is that because SharePoint is such a flexible (large?) product is that many of them find it difficult to get into quickly. I can understand this as it can be an awful lot to take in.

However, I really do think many partners are missing out on revenue opportunities because of this! Now that don’t necessarily mean you need to instantly became a master in SharePoint but if you have a basic understanding of what it can do then you can always partner with a company that does if you have a client who might benefit from such a solution.

Partnering with other companies is something SBSC partners are good at!

So….what I’m going to try to do in the time I’ll have is to create a basic helpdesk. All IT companies know what a helpdesk is and what sort of functionality it needs so we can create a quick and dirty SharePoint application that showcases what SharePoint can do.

I’ll be touching on,

Lists and Libraries.

Columns and Views.

Content Types and E-mail Integration.

Web Part Pages and Web Parts.

SharePoint designer and Workflows.

Office integration and Mobile access

And if there is time another topic I like to shout about…InfoPath

Time depending of course!

Our other speaker is Dell Quinn from Microsoft.

She’s going to talk about the changes to the Microsoft Partner Network and how it’ll impact Small Business Specialists.

All this as well as the usual pre and post event banter that goes on at any AMITPRO event!

As always guests are more than welcome. If you’ve never attended a user group event we’ve love for you to come along.

If you’d like to know more than leave a comment here, visit the AMITPRO site or get in touch with me directly (or on Twitter)

Look forward to seeing you there!

In part four I mentioned that there would be a problem in the future with this solution.

In the second part of this series we created a simple function that generated a HTTP request to send to the Twitter API.

As part of that request we sent a username and password.

This known as “basic authentication”

Unfortunately just after I got this working the Twitter development team announced on google groups they are dropping support for basic authentication.

our plan is to turn off basic authorization on the API by june 30, 2010 — developers will have to switch over to OAuth by that time.  between now and then, there will be a *lot* of information coming along with tips on how to use OAuth Echo, xAuth, etc.  we really want to make this transition as easy as we can
for everybody.

Twitter even created a site called “Countdown to oAuth”

I can understand why Twitter have done this as it’ll make the system far more secure.

Unfortunately this breaks my solution so I’ll need to take a look to see how i can use a different authentication method.

I’ve got till the end of June so hopefully I’ll get something sorted soon!

Just one final post on the way to wrap this up.

In part three I said there was bit of functionality left to clear up.

We have to run the process manually.

We actually did a little bit of the ground work in part two.

One of the pieces of code was the main function that brings all the bits and pieces together – it was called “Fetch_Tweets”

Public Function Fetch_Tweets() As String

Dim strID As String
Dim strXML As String

If Get_Settings = False Then
    Debug.Print "Couldn’t get settings"
    End
End If

strID = Get_Last_Tweet_ID
strXML = Get_Latest_Tweets(strScreenName, strUserName, strPassword, strID)

SaveTmpXML strXML

Application.ImportXML strTempFile, acAppendData

Tidy_User_table

End Function

Take a look at the first word of this code block.

PUBLIC

By adding this we can reference the function outside of Access so I put together a vbscript to run the function. (essentially…programmer types will argue this isn’t what Public means but for the layman it’ll do here!)

Dim TweetDB

TweetDB = "C:\TweetPoint\Twitter.ACCDB"

Dim myAccess
Set myAccess = CreateObject("Access.Application")

myAccess.OpenCurrentDatabase TweetDB, False
myAccess.AutomationSecurity = msoAutomationSecurityForceDisable

myAccess.Run("Fetch_Tweets")

myAccess.CloseCurrentDatabase
myAccess.Quit acQuitSaveNone
Set myAccess = Nothing

So just breaking this down.

The vbscript is essentially doing exactly the same as if you were running this manually.

First we create an instance of Access. (The same as opening the application)

Then we open the database we need.

Then we tell Access to run our “Fetch_Tweets” function.

The we close the database and close the application.

Simple!

The only caveat here is macro security. If you have your security in Access set to high or prompt then the vbscript won’t work.

Since I’m just doing this a proof of concept I turned the macro security off.

You’ll need to make your own decision about how to deal with this.

One suggestion though is to look at something called “Trusted Locations”

This article explains how to set that up.

We can then take this vbscript and run it as a scheduled task to run as often as you need.

The major downside to this is that the system that will run the vbscript will need to have Access installed.

I don’t think the Access runtime would be enough (I only tried it very briefly)

So that’s all of our basic functionality problems sorted

We can ask Twitter to return the tweets for a given person, have them displayed in a SharePoint list automatically and it will be intelligent enough to not give us duplicates.

I’ll follow this up with a couple of posts that shows how to add a little more polish and cover a problem that I’ll need to look at going forward. I haven’t figured out what to do about it yet though!

Following on from part two I commented that there were a couple of issues outstanding,

1. It doesn’t automatically update the SharePoint list. We have to repeat the list creation process every time.
2. We have to run the process manually. 

This post will cover the first item on the list and is really straight forward.

Go back to the first post and make sure that you have created your list on your SharePoint site by exporting it. (Go now, I’ll wait).

Once it’s done in the Access Database delete the “status” table (or rename it if you want to play it safe).

Then from the “External Data” tab select the option to “Import SharePoint List”.

The wizard will start – enter your site name and select the option.

“Link to the data source by creating a linked table”.

Click Next to display the lists you can import.

Choose the list (I’ve called mine “TweetPoint” – think it’ll catch on?)

Click OK to link the list.

You’ll then see the SharePoint list alongside the other Access tables.

User Information List is also linked as this holds user information which will be entered onto the list for things such as the “Created by” field.

Now the clever bit to hook it up to our Twitter API calls.

Bear with me because this is really complex

Right click on your newly imported list and select the rename option

Change the name to “status”

Done! (ok I may have exaggerated how difficult this was)

So what’s actually happened here?

We’ve changed the name that Access uses to reference the table.

In the background it’s still hooked up to SharePoint via it’s URL so any changes we make on the table will automatically be updated on the SharePoint side!

The import process we created in the first post is expecting to append the data to a table called status (since that is what the Twitter API returns) so that is exactly what we’ve provided!

Only one thing left to clear up in the next post!

I intended to follow on from part one a bit sooner but it’s been really busy at the office!

In part one I gave a brief overview of what I was trying to accomplish and how to get a rough prototype working.

While it did the job I highlighted the following limitations.

1. It only fetches the last twenty updates – if there have been twenty five updates since you last did it then you’re out of luck.
2. Conversely, if there have only been a few updates it’ll still fetch the last twenty giving you duplicate items.
3. There is also the problem of needing to run this manually. 
4. It doesn’t automatically update the SharePoint list. We have to repeat the list creation process every time.
5. Finally, it doesn’t deal with protected Twitter accounts at all!

This post will deal with the items 1, 2 and 5 and is actually pretty easy.

We’re going to use a bit of VBA to make Access a little smarter. I’m not a programmer/developer so if the code looks silly or inefficient….there is a good reason for it!

Also you’ll notice a distinct lack of error handling. This is just an exercise to see if it would work so code is kept to a minimum!

The Twitter API method I used in the previous post had a parameter where you can specify a tweet ID and the API will return all tweets since then.

http://api.twitter.com/1/statuses/user_timeline.xml?screen_name=AndyParkes&since_id=13081868261

So the only difficulty now is actually figuring out what tweet ID to use.

If only we had some sort of list we could query to do this.

Again this is really easy as we’re using Access which is built for the job!

Here’s the bit of SQL I crafted

"SELECT TOP 1 VAL(status.id) as TwitID FROM status ORDER BY VAL(status.id) DESC;"

I’m using the VAL function to convert the tweet ID to a number as I had some weird sorting issues.

I wrapped this is in a VBA function called “Get_Last_Tweet_ID”

Function Get_Last_Tweet_ID() As String
Dim db As Database
Dim strSql As String
Dim rstData As DAO.Recordset
Dim strID As String

Set db = CurrentDb()
strSql = "SELECT TOP 1 VAL(status.id) as TwitID FROM status ORDER BY VAL(status.id) DESC;"

Set rstData = db.OpenRecordset(strSql)

    If rstData.EOF = False Then
        strID = rstData("TwitID")
    Else
        strID = ""
    End If

    rstData.Close
    Set rstData = Nothing

Get_Last_Tweet_ID = strID

End Function

So this function will simply return a tweet ID we can plug into the API call and it’ll only return the most recent tweets. If the function returns an empty string we just don’t bother to run the API call.

The next question you’re probably asking is HOW do you run the API call?

Remember the wizard we ran in the last post to import the XML? All that wizard does is use a VBA function called ImportXML

The syntax is simple

Application.ImportXML(DataSource, ImportOptions)

The parameters are the same options asked for by the wizard.

A data source and whether you want to import the data, the structure or both.

That’s the first part – but since I want to be able to take protected accounts into consideration we can’t just drop a URL straight in as the data source (where would you put your username and password!)

So we’ll just fashion the request ourselves.

We’re sending a request to a web service to get response back with some XML so the object we’ll use is XMLHTTP and it will send a GET request to the Twitter API which should throw back a chunk of XML.

Function Get_Latest_Tweets(strScreenName As String, strUser As String, strPassword As String, strLastID As String) As String

Dim myXML As MSXML2.XMLHTTP
Set myXML = New MSXML2.XMLHTTP

If strLastID = "" Then

    myXML.Open "GET", "http://api.twitter.com/1/statuses/user_timeline.xml?screen_name=" & strScreenName, "False",     strUser, strPassword
Else

    myXML.Open "GET", "http://api.twitter.com/1/statuses/user_timeline.xml?screen_name=" & strScreenName &     "&since_id=" & strLastID, "False", strUser, strPassword
End If

myXML.send

Get_Latest_Tweets = myXML.responseText

End Function

Note: Depending on what you have on your machine you may need to use “Microsoft.XMLHTTP” instead.

This function takes a couple of parameters, the ScreenName of the Twitter account to retrieve, a username and password for authentication and a Tweet ID.

We check to see if we passed an ID. If not then don’t use the “since_id” parameter and just fetch the last 20 tweets (the default). We could add an extra parameter to fetch a specific number of tweets.

We then send the response and the function returns a string containing some XML.

Now that we have our XML from Twitter what now?

Since the ImportXML wizard requires a file to work with we need to save the XML to disk.

Sub SaveTmpXML(strXML As String)
     ‘ Load the XML
     Dim xmlDoc
     Set xmlDoc = CreateObject("Microsoft.XMLDOM")
     xmlDoc.async = "false"
     xmlDoc.loadXML strXML
    xmlDoc.Save strTempFile
End Sub

This is a really simple procedure. We pass the XML to it, create an XMLDOM object, load the XML string and save it disk. I used a global variable for the filename so I can specify a temp path in an options table which I’ll cover later.

Finally we can import the XML into our table,

Public Function Fetch_Tweets() As String

Dim strID As String
Dim strXML As String

If Get_Settings = False Then
    Debug.Print "Couldn’t get settings"
    End
End If

strID = Get_Last_Tweet_ID
strXML = Get_Latest_Tweets(strScreenName, strUserName, strPassword, strID)

SaveTmpXML strXML

Application.ImportXML strTempFile, acAppendData

Tidy_User_table

End Function

This a wrapper function that calls all the code I’ve outlined above.

We find the last Tweet ID, fetch the tweets from Twitter, save them to an XML file and finally import them into our table.

You’ll notice the Get_Settings and Tidy_User_Table procedure calls, I’ll also cover those in a later post.

You could hook this wrapper function up to a button on a form. Once clicked it would update the table in the database with the latest tweets.

I think that’s all three issues solved. We now only fetch exactly the tweets we need and can work easily with protected tweets (Twitter recently announced a change that will break this but I’ll cover that in an upcoming post)

I’ll get part three together a bit sooner!

This is going to be quite lengthy so I’ll split into a couple of posts.

Back in March, Mark Wilson of MarkWilson.co.uk (if you’re not reading his blog….go check it out now!) asked the following on Twitter.

Does anyone know how to read XML (i.e. Twitter updates) into a SharePoint List (not the XML webpart reading it dynamically)?

Since I like a challenge I decided to take a look at it.

If you search (using your favourite search engine) for Twitter and SharePoint you’ll find one of two things.

Either, examples of how to use a webpart to grab the RSS feed of someone’s Twitter status or people creating a Twitter-like application using SharePoint (which is pretty cool anyway).

What Mark was looking for was something slightly different.

He wanted to collect posts from a specific user into a SharePoint list. In effect creating an archive that a team could view. They could even use SharePoint to create views to look for keywords.

This meant the webpart wouldn’t do as it only shows a snapshot of the current status updates. If the particular user tweets quite a lot you could miss stuff.

Mark initially pointed me in the direction of the RSS feeds for each user (here’s mine) but this gives us a similar problem to the webpart as it only shows the last 20 tweets.

This was when I stepped out of my comfort zone and started looking at the Twitter API 

It turns out the Twitter API isn’t actually very complicated. All you need to do is craft a URL to pass certain parameters and it’ll throw some XML back at you.

For example,

This url will retrieve an XML file containing my last five tweets.

http://api.twitter.com/1/statuses/user_timeline.xml?screen_name=AndyParkes&count=5 (you can click this even if you don’t have a Twitter account. Authentication is only needed for protected accounts)

So I’d now found a way of grabbing the tweets…but how to get them into a SharePoint list?

IF I were a SharePoint developer armed with a copy of Visual Studio I actually don’t think this would be all that difficult to do. (you’ll see why in one of the later parts to this post)

However, since I’m not I need to make use of the tools at my disposal.

I had to think of something that can make use of XML but also talk to SharePoint and the answer is….

Microsoft Access

Yep..seriously.

Access has the ability to import XML files into a table.

Access also has the ability to link to a SharePoint list and update it.

By putting these two bits of functionality together I was actually able to reach the desired effect.

You can try it yourself.

Open Access and create a new blank database.

Click the External Data tab and choose XML file.

Access 2010 screenshot – procedure is similar in Access 2007 though

Enter your API URL into the file name field. The URL I’m using will return my last 20 tweets

You’ll be prompted to verify the import

Choose structure and data first time round so you actually create the tables

On subsequent runs you can just append the data

Done…you can save the import steps if you want so you can repeat this without going through the whole wizard again.

I’ve now got my last 20 tweets into an Access database.

You’ll notice there are actually two tables created.

Status contains the tweets.

User contains the details about the user this is being pulled from –it’s part of the XML returned.

So to get it into SharePoint.

Select the status table, click the External Data tab again this time use the Export section and select SharePoint list.

Run through the export wizard.

Choose a destination site.

You’ll see it creating the tables.

Done!

You can then browse to your site and view the list!

You can also create a view to just show the important fields.

TaDa!……well not quite.

Currently it’s not very dynamic.

All it does is fetch the last 20 updates. If you re-ran the process above again you’d run into problems doing the SharePoint export as the status table already exists you’d end up with multiple lists (eg. status, status_1, status,2)

Also it’s not smart enough to realise that if we already have some tweets in the database we don’t want to re-add those. If you followed the procedure above for a second time you’d also end up with duplicate tweets.

Finally if you tried to put them into chronological order you may notice the sort doesn’t quite work under certain circumstances.

So in the next part we’ll put Access to work to make this a bit more intelligent and finally automate the whole thing so it’ll fetch the tweets all by itself!

I got an email earlier this week from Richard Tubb asking a couple of questions about InfoPath.

This is also the same Mr Tubb who has been “nagging” me to post more about InfoPath and SharePoint. I do take his point as I’ve posted very little on the topic since I spoke about it at AMITPRO last year (can’t believe it’s been nearly 12 months since that!)

So….InfoPath!!

I’ll talk about InfoPath in the Office 2007 world at the moment. Even though the latest version is upon us the current version will be hanging around for a while. Also the skills are transferrable and I’ll need material for future posts right?

What is InfoPath?

In a nutshell it’s all about electronic forms.

If you’ve ever created a form in Microsoft Access it’s along similar lines. What’s cool about InfoPath though is that it isn’t tied into a specific database system. It can talk to SQL Server, Access databases, SharePoint (which is is it’s main strength) and more. You can even make use of InfoPath forms within Outlook to gather information via e-mail!

I also think that when stacked up against a form in a Word document InfoPath wins a lot!

InfoPath allows you to do form validation to ensure data is entered correctly.

It’s biggest strength is it’s capability to “unlock” data which a Word document just can’t do. (Unless you want to do a lot of VBA coding)

This means an simple example is in order.

Lets say you had a Word document that your staff used to enter their weekly hours worked.

It might look like this.

As you can see there is a lot of important information here.

At the top we have data that lets us know who the time sheet belongs to, and when it’s for.

Moving down we have the actual data itself.

The hours worked.

Finally we have a brief summary of data so you can see at a glance what’s going on.

So what’s wrong with this?

Data Validation

You would have to trust whoever fills out the form to put a date in right place and numbers in the hours worked fields. What if someone enters 25 hours for single day? What if “Sales” isn’t even the correct name of the department?

Now you can sort of do this in Word 2007. But it’s not exactly simple. In fact, good luck finding how to insert a form field – The developer tab is hidden by default (I’ll explain how to display them in another post). Then you have to contend with “legacy form controls” and the new Office 2007 form controls. Not fun at all!

Calculations

Once again you’d need to trust whoever is filling out the form to get their maths right. As with data validation you can get Word to do calculations on tables but it’s not exactly simple or intuitive!

Trapped Data

This is the biggie!

I’ve only showed you one form. Let’s imagine you’re Mr Anderson’s line manager. Your boss walks up to your desk at 9am Monday morning and tells you that your department is spending a fortune in overtime. He wants to know exactly how many hours your department logged in overtime for the last three months overall and on a per-person basis…..and he wants it for the management meeting at 11am!

So lets say that each person would have 4 timesheets per month. That’s 12 per person.

If your department had 5 people in it that’s 60 Word documents you need to open, read through, check the maths and note the important figures to bring into your total summary.

That’s going to take some time!

How does InfoPath help?

Here’s the same form designed in InfoPath

At first glance you’ll notice it’s essentially the same form as before

But if you look in the first block of data

You can see a calendar control button. This means I can choose a date with the mouse as well as typing one in.

It won’t let me put anything other than a date in the field.

You’ll also notice all the fields in the first section have a red star next to them.

This because I’ve made them mandatory fields. It’s a little visual notification to remind the user to put some data in.

You also get InfoPath to pop up a little message if no data is entered!

The fields that contain the hours worked data also have some validation rules.

This screenshot shows I’ve tried to enter some text in a numeric field

We get the nice red dotted border AND a tooltip to let me know what’s wrong.

What’s really cool about this is that I didn’t even need to set this up. Just by specifying that the field was numeric InfoPath setup the basic validation for me.

Each control has LOTS of options around data validation to make sure we get exactly the correct data in.

You may also have noticed that the department field is a drop down list.

This means that we can ensure that only valid departments are entered. You’ll see why this can be quite important later on.

Also, the data is actually pulled in from a SharePoint list.

This means that these lookup lists can easily be managed without having to edit the InfoPath form. We can also set security on the SharePoint list to ensure only specific people can make changes to the department details.

InfoPath also has rules and events we can work with. We could actually set this up so all the staff names appeared in another drop down and that once a department has been chosen only the staff in that department are shown (or vice versa. You choose your name and your department is automatically filled out)

This totally solves the Data Validation problem I mentioned above.

So what about calculation?

Easy!

Same form as above with the same data entered

However this time the summary data is updated automatically.

I’ve set the summary fields to do a simple bit of addition and then made them read-only so they just work on there own without any user input needed!

Sorted!

Data Validation and Calculation all dealt with quickly and easily.

I could understand if you were still a little sceptical at this point though. As i said lots of similar functionality is already available all across the Office suite. That brings me onto the final point I made above.

Trapped Data

The real magic happens when this is published to a SharePoint site.

When I published the form I specified that I wanted the summary fields to be pushed through to the SharePoint form library.

This is called “property promotion”.

Here is the time sheet Tom Anderson just filled out on the SharePoint site.

I can now see how many hours Mr Anderson worked that week without even opening the file!

Multiply this across the whole team and you can see at a glance what everyone was up to!

Let’s throw a bit of SharePoint magic in.

I’ve grouped by Department and then by Week Commencing Date.

Can you see why it was important to get the department entry consistent?

We can now get a real overview of the hours entered by each person.

And one finishing touch.

I’ve asked SharePoint to sum the totals fields.

This can look a little confusing your grouping as it gives you overall totals as well as a total at each group level. You’d be better setting up a filtered view to do this.

Something like this.

I’ve removed a level of grouping and filtered to only show the Sales team.

You can now see really easily over the last two weeks the Sales team have posted 18 hours of overtime.

Just to show off….you could then dump this out to Excel for further analysis.

I created that chart with about five clicks of the mouse. Getting that report together for the boss would be nice and simple.

Finally one other cool thing about using SharePoint and InfoPath for a solution like this.

The files themselves are stored in XML format

This means if yoy needed integration with another system (your accounts package for example) this makes the whole thing a lot easier.

I’ll stop there….this was supposed to be a quick introduction.

If you’ve made it to the bottom of this post thanks for the reading!

This was just one example of how you can use InfoPath in a real world scenario.

There is lots more you can do, especially when you put it together with SharePoint.

For example, imagine having an expenses form tied into a workflow so that management approval is required when a certain monetary threshold is met?

Hopefully this all makes sense and you can see why I’m such a fan of InfoPath!

Please comment if you want me to post more about InfoPath and I’ll be happy to do so

*I’ve just noticed all the dates are in US format….I didn’t change the regional settings on my newly created test site…..i’m not re-doing the screen shots though! *

With everything that’s been going on personally and professionally the last few months the newest version of Office sort of skipped by me

Sure I installed the “alpha” when it was released on one of my machines but I wasn’t using it full time

Yesterday I had to do a rebuild of my main office PC so I took the opportunity to install the Beta

This post isn’t about the shiny new features though, it’s about the different suites you’ll be able to purchase

This time around we get four retail versions (from the Office 2010 engineering blog)

Office Home and Student1	Office Home and Business	Office Professional	Office Professional Academic
Word 2010	Word 2010	Word 2010	Word 2010
Excel 2010	Excel 2010	Excel 2010	Excel 2010
PowerPoint 2010	PowerPoint 2010	PowerPoint 2010	PowerPoint 2010
OneNote 2010	OneNote 2010	OneNote 2010	OneNote 2010
	Outlook 2010	Outlook 2010	Outlook 2010
		Publisher 2010	Publisher 2010
		Access 2010	Access 2010

On first glance I’m really pleased

OneNote for everybody!!!

However on second glance I’m a bit gutted as you’ll notice that once again there is no InfoPath unless you buy Office via licensing (Office Professional Plus for most businesses)

I commented before on how I think a lot of smaller businesses are missing out because InfoPath is inaccessible to them

It’s frustrating when we can sell Small Business Server 2008 with one of the key features being the inclusion of SharePoint and then not being able to create some really great solutions because a key piece of software isn’t as easily available. A quick search found Infopath 2007 box product to be somewhere in between £100-£140. Licensing is obviously different but if you’re going down that route you may as well just get Professional Plus

So it’s left to the SBS team to save us! Here’s my idea,

If you ever release SBS 2008 R2 (and I understand that is IF) can we get some InfoPath licenses added to the Premium CALS? 

I know that is unlikely to happen but a guy can wish right?