Bill - thanks for the suggestion - it's a tempting idea but I don't think that translating 3,000 lines of VBA into J is a good use of my time, especially when the purpose of the exercise is to test the existing code.
On Thu, Apr 28, 2011 at 12:13 AM, bill lam <[email protected]> wrote: > I think you do not need using macro. All programmable properties of excel > should already been exposed from idispatch interface. Try translate the > vba code into J oleautomation. If some vba code cannot be translated to J > oleautomation, such as safearray, then try wdooo. (untest) > > -- Devon McCormick, CFA ^me^ at acm. org is my preferred e-mail ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
