On Wed, May 21, 2014 at 10:49 AM, Alan Cassidy <ACassidy@xxxxxxxxxxxxxx> wrote:
As I explained, the politics where I am right now are such that
there were "political" barriers right now to setting up for POI.
When I first read that, I was a little confused. Not about political
barriers, but about "as I explained". But due to a random mention in
another thread about the PCTECH list, I now know that a big chunk of
your explanation was over there.
And that's where I saw that you were also investigating automation of
the Excel-to-XML process. And, if I'm reading it right, that the
parent IT department (or whatever department you may be merging into)
is a .NET shop.
Well. That is a horse of a completely different color. If the
"political barriers" are less to do .NET, particularly for an
Excel-centric project, then my recommendation is (or at least would
have been, had I known this earlier), by all means, use .NET! The
baked-in support for Excel is so much stronger and so much easier to
use from within .NET that it's almost a crying shame to do it any
other way, when that way is available.
And if not .NET, then a whole host of Windows or platform-neutral options.
Ah well. For next time, maybe.
John Y.
As an Amazon Associate we earn from qualifying purchases.