The division of the bank in which I work have set a policy that frowns very heavily on the use of C#, strongly encouraging that all developers use only Java instead - although things like Sybase are of course allowed. VBA is also still allowed, but MS are gradually reducing support for it, in favour of VB.NetI understand that JIntegra can be used to control Excel files from Java. Thing is, that I thought C# was meant to be quite good at manipulating anything Microsoft based.Is trying to use Java + JIntegra to manipulate Excel files the equivalent of flogging a dead horse, or does it actually work reasonably well ?Any opinions gratefully received

I have used both JIntegra and cheaper COM libraries for Java.They all work pretty well if all you need to do is to act as a COM client.For the Excel case they also come with lots of examples and tutorials.I did not feel C# had much of an advantage in this case.If, on the other side, you wanted to create COM servers then it seems to me thatC# has better support with tools and libraries. In that case one can also notice differentlevels of support from different Java libraries where I think JIntegra comes on top.In your case you only need to be a COM client to use Excel to control Excel files.So you are not losing much by being forced to use Java. A curious thing is that if you use JIntegra you can access Excel form a Unix machine. Of course you still need a Windowsmachine to run Excel, so I am not sure this is a great advantage.

VBA is also still allowed, but MS are gradually reducing support for it, in favour of VB.NetVBA is in Excel 12, I'm one of the tech beta testers, so that's a hard data point. VBA will be in Excel for the forseeable.I'm with asimegi, C# is much better than Java for controlling Excel externally, but my experience is that no language actually does it well, and your productivity will be much lower than VBA in most cases.Although the bank "frowns" on C#, getting the job done robustly and swiftly is a lot more important in most cases. Jintegra isn't bad, though I found myself writing vastly more code to do things that were quick in VBA.Both languages execute more quickly than VBA, but usually you lose far more in crossing the process boundary.What about C++ ?

QuoteOriginally posted by: dj99The division of the bank in which I work have set a policy that frowns very heavily on the use of C#, strongly encouraging that all developers use only Java instead - although things like Sybase are of course allowed. VBA is also still allowed, but MS are gradually reducing support for it, in favour of VB.NetI understand that JIntegra can be used to control Excel files from Java. Thing is, that I thought C# was meant to be quite good at manipulating anything Microsoft based.Is trying to use Java + JIntegra to manipulate Excel files the equivalent of flogging a dead horse, or does it actually work reasonably well ?Any opinions gratefully receivedFor every choice you have to weigh up the advantages and disadvantages. I find the use of the word 'frown' intriguing here. Using C# and Excel is fine; Microsoft s/w tends to work well with Microsoft s/w. And the .NET framework is a nice environment to work in.

If there is one thing that really irritates me it's technology departments who issue edicts (and I could end the sentence here…) that "thou shalt use java", without regard for the constaints this has to cause for people concerned more with development for the on-desk software - which is pretty much exclusively microsoft.Do your best to put them in their place…the desks productivity has to come first, because without it there would be nobody making the money that pays for those IT guys to sit there all day reading/frowning over their java books.i work in a shop that wound up scrapping a multi $m spreadsheet system replacement project due in one large part to restrictions caused by the conversation between Excel & JIntegra.

QuoteOriginally posted by: patch22If there is one thing that really irritates me it's technology departments who issue edicts (and I could end the sentence here…) that "thou shalt use java", without regard for the constaints this has to cause for people concerned more with development for the on-desk software - which is pretty much exclusively microsoft.Do your best to put them in their place…the desks productivity has to come first, because without it there would be nobody making the money that pays for those IT guys to sit there all day reading/frowning over their java books.i work in a shop that wound up scrapping a multi $m spreadsheet system replacement project due in one large part to restrictions caused by the conversation between Excel & JIntegra.Reading you loud and clear.

I'm with patch22 100% here.Deliver something that works, deliver it soon and things should work out.You may find it politically expedient to call it a VBA prototype (or C#)A lot of really important work is done by "prototypes" However, this is not the "fault" of the IT department as such. It's the bonus structure which is largely dictated by front office and acocuntants.Front office don't want IT people in their bonus pool, and force the creation of a separate bonus pool that is both under funded and not in their control.Then they wonder with wide eyes why IT people care about making IT bosses happy, not traders.IT boss says use Java = get bonus + promotionTrader says Java = longer development times + lower profit for the bank.For most IT types, that's a very easy decision, but not the one you want.IT departments make this sort of decision because the accountants focus on observable costs, and "success" for too many IT managers is staying within budgets that have no input for tactical issues. Saying "deliver a new email system for $2 million" is a viable goal, but "keep the traders happy by spending X" is not.