October 26, 2007 at 2:45 am
We currently have a VB6 COM object which is called from a SQL stored procedure to read tables and add appointments in to users Outlook calendars.
We've tested our system on a x64 SQL 2005 and the 32bit com object can't be instantiated. :unsure:
We're rewriting the code as a CLR in VB.net but are unable to add a reference to Interop.Outlook because it is not an Assembly in SQL server, when trying to add the interop to SQL Server we get error about the version of stdole.dll etc.... :crazy:
Does anybody have any idea how we can integrate with the Outlook Calendar from a CLR?? :crying:
October 26, 2007 at 3:35 am
better check this!!!!!!!!!
microsoft.apress.com/asptodayarchive/72409/creating-a-tv-guide-style-multicast-scheduling-system-using-vb
dotnet.sys-con.com/read/46614.htm
download.microsoft.com/download/f/c/5/fc502411-afd8-4fa2-8572-ffe11187f0e2/Session1.ppt
appointments.alienpicks.com/
blogs.msdn.com/toub/archive/2004/05/22/139609.aspx
October 26, 2007 at 6:49 am
For a relatively safe approach with the least amount of development and testing, wrap your existing com object in a web service and publish the web service on a 32 bit web server.
Then, all you have to do is reference and call the web service from the CLR on your 64 bit server.
October 27, 2007 at 2:41 am
If you register your 32 bit VB6 COM object as a COM+ component you should be able to instantiate it in SQL 2005 x64
____________________________________________________
Deja View - The strange feeling that somewhere, sometime you've optimised this query before
How to get the best help on a forum
http://www.sqlservercentral.com/articles/Best+Practices/61537Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply