Hi,
I'm going to develop a server side component for a VBA front-end (Excel). I use VS.Net 2003. Is DCOM the way to go What are other options
PS I've been developing COM components for VBA in .Net for quite a long period, and managed to make all I wanted. The main thing I wonder is if using DCOM instead of local COM seamless, or there're special issues
Ruslan
Server side for VBA - DCOM? .Net?
xbrady
You've got Excel running on the client, a component running on the server...
I'm wondering why the component isn't on the same machine as Excel Is it because the component is accesses something specific to the server Because the component is servicing multiple requests Because Excel is being used by a web page Why are you considering a distributed model
There are other options such as a web service or a grid object. It all depends on the real problems you are trying to address. It would be easier to recommend alternative technologies if the requirements where clearer.
Thanks,
Kim Greenlee
da Vinci
I agree with Kim, that you need to give more details on the context
Just a quick comment on your client side choice (VBA) - you may also want to consider VSTO 2005 - which lets you build excel templates in C# (see for example http://msdn.microsoft.com/office/understanding/vsto/default.aspx pull=/library/en-us/odc_vsto2005_ta/html/officevstobuildingexcelinvoices.asp)
Arnon