Application lost Outlook connectivity?

[Pheasant Plucker®]

Hi there,

Not sure if this is the correct ng and I am not a programmer so excuse me
but here goes...:-)

We have a custom application that has a hook or calls either the Outlook
calendar or looks in the Inbox
for a specific email and acts upon it if found.

This has worked great for over a year but when I updated using the usual
Microsoft Update site around the beginning of December we have since lost
connectivity to Outlook altogether.

This means we are unable to import/export our work from/to Outlook from
within our application.

I cannot be sure if this is related to any specific .NET Framework update or
not as out of 7 TabletPC's I have updated only 3 exhibit this lost
connectivity with Outlook - mine and the programmers included :-(

I have listed the error message below my sig if that is of any help in
diagnosing what has gone wrong and more importantly finding a solution.

The programmer has suggested uninstalling and then re-installing Office 2003
suggesting that the fault may be caused by the GAC that should reside in
Windows\Assembl y having been removed by a recent .NET Framework update from
Microsoft.

I can see where he gets the idea from looking at the error log below but I
am not convinced because when I looked on a couple of the updated TabletPC's
this directory was not present but the application worked as it has always
worked...

He also suggested re-installing the Primary Interop Assemblies but this did
not cure the problem on my own TabletPC...:-(

Does anyone know what the answer might be please?

Uninstalling/re-installing Office is a last chance option - I wonder if
uninstalling .NET entirely and then re-installing it might solve it.

Can some kind soul help or point me to a resource that might help please?

--
Thanks & regards,
-pp-

Error message from within our custom application;

An unhandled exception has occurred in your application. If you click
Continue, the application will ignore this error and attempt to continue. If
you click Quit, the application will be shut down immediately.

The specified module could not be found.

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.IO.FileN otFoundExceptio n: The specified module could not be found.
at WinTestAPP.Main _Screen.Picture Box1_Click(Obje ct sender, EventArgs e)
in E:\nukmost\Tabl et PC Application\Mai n_Screen.vb:lin e 190
at System.Windows. Forms.Control.O nClick(EventArg s e)
at System.Windows. Forms.Control.W mMouseUp(Messag e& m, MouseButtons
button, Int32 clicks)
at System.Windows. Forms.Control.W ndProc(Message& m)
at System.Windows. Forms.ControlNa tiveWindow.OnMe ssage(Message& m)
at System.Windows. Forms.ControlNa tiveWindow.WndP roc(Message& m)
at System.Windows. Forms.NativeWin dow.Callback(In tPtr hWnd, Int32 msg,
IntPtr wparam, IntPtr lparam)
************** Loaded Assemblies **************
mscorlib
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.2407
CodeBase:
file:///c:/windows/microsoft.net/framework/v1.1.4322/mscorlib.dll
----------------------------------------
CCC_Data_1
Assembly Version: 1.0.2901.27638
Win32 Version: 1.0.2901.27638
CodeBase: file:///C:/Program%20Files/Hemini%20Plc/UKMOST/CCC_Data_1.exe
----------------------------------------
System.Windows. Forms
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.2032
CodeBase:
file:///c:/windows/assembly/gac/system.windows. forms/1.0.5000.0__b77 a5c56193
4e089/system.windows. forms.dll
----------------------------------------
System
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.2407
CodeBase:
file:///c:/windows/assembly/gac/system/1.0.5000.0__b77 a5c561934e089/system.d
ll
----------------------------------------
System.Data
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.2032
CodeBase:
file:///c:/windows/assembly/gac/system.data/1.0.5000.0__b77 a5c561934e089/sys
tem.data.dll
----------------------------------------
System.Xml
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.2032
CodeBase:
file:///c:/windows/assembly/gac/system.xml/1.0.5000.0__b77 a5c561934e089/syst
em.xml.dll
----------------------------------------
System.Drawing
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.2032
CodeBase:
file:///c:/windows/assembly/gac/system.drawing/1.0.5000.0__b03 f5f7f11d50a3a/
system.drawing. dll
----------------------------------------
Accessibility
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.573
CodeBase:
file:///c:/windows/assembly/gac/accessibility/1.0.5000.0__b03 f5f7f11d50a3a/a
ccessibility.dl l
----------------------------------------
Microsoft.Visua lBasic
Assembly Version: 7.0.5000.0
Win32 Version: 7.10.6001.4
CodeBase:
file:///c:/windows/assembly/gac/microsoft.visua lbasic/7.0.5000.0__b03 f5f7f11
d50a3a/microsoft.visua lbasic.dll
----------------------------------------
Microsoft.Offic e.Interop.Outlo ok
Assembly Version: 11.0.0.0
Win32 Version: 11.0.8161
CodeBase:
file:///c:/windows/assembly/gac/microsoft.offic e.interop.outlo ok/11.0.0.0__7
1e9bce111e9429c/microsoft.offic e.interop.outlo ok.dll
----------------------------------------

************** JIT Debugging **************
To enable just in time (JIT) debugging, the config file for this
application or machine (machine.config ) must have the
jitDebugging value set in the system.windows. forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuratio n>
<system.windows .forms jitDebugging="t rue" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the machine
rather than being handled by this dialog.