lookUp.Items.Add(ControlFactory.CreateLookupItem(1, "{" + oAccount.accountid.Value.ToString() + "}", oAccount.name));

When the link in the lookup is pressed it does not open the entity on the CRM server. It seems to be using the servername and port of the page the lookup is on is running on, rather than the CrmUrl value in c360.config file. For example the url referenced when running on localhost is http://localhost:3333/sfa/accts/edit.aspx?id={62c56cb7-f773-db11-af2f-000c29b74382}&  when it should be http://CrmUrl/sfa/accts/edit.aspx?id={62C56CB7-F773-DB11-AF2F-000C29B74382}

Are you able to reproduce this?

Make sure you have spelled the "CrmUrl" key correctly (careful it's case sensitive). Also, sometimes the VS.NET developement web site sometimes doesn't automatically detect changes to the c360.config and I sometimes have to stop and restart it to make sure my changes take effect immediatly.

<add key="CrmUrl" value="http://DevServerIP/" />

I am able to reproduce the problem you are describing at will when I:

1. Omit the CrmUrl from my config file. In this situation, when I click on a lookupItem the URL is http://localhost:24816/sfa/accts/blablabla
2. Mistype the name of the key. Since this key is in a XML file, the name is case sensitive so it's easy to make a mistake.
3. Type an invalid value for this key. In this situation, when I click on a lookupitem the URL is http://wrongservername/sfa/accts/blablabla

However, when I correctly enter the key in the config file with the appropriate value it works perfectly. In this situation, the URL is http://localhost:5555/sfa/accts/blablabla

The CrmUrl is the one and only key that controls the URL when our SDK needs to open CRM pages.

I will test adding items programatically this afternoon and will let you know the result.

This is indeed a problem with our SDK and I have reported it as defect number DE1570