Hi,
I'm curious to see if you can get this running. OLE based automation was a
little flakey with MS based languages even when this was in vogue. Fingers
crossed.
Typically in the past it was better to flick these switches before running
before kicking off any type of process:
Application.Calculation = xlCalculationManual
' only if needed i.e. perhaps cells need to be initialised?
' Application.Calculate
Application.ScreenUpdating = False
' sometimes you need to force excel to calculate stuff
' or be very specific for massive workbooks
' e.g.
' Range("A1:C20").Calculate ' normally only useful if in "manual"
mode or if Excel is confused (e.g. old excel files that need to be rebuilt).
The xlCalculationManual switch is important. It will turn off the Excel
parsing / calculation engine.
Also, often it was better to put Excel in charge through throwing a button
on an excel sheet + running VBA code. e.g. button -> vba -> J code
(I haven't used J with Excel. I can't comment on how well this will work).
The approach for one of the largest excel users was to put the bare minimum
load on Excel through writing xll addings. That'd normally pertained to
live feeds or reference data imports.
Perhaps I'm paranoid, but I "feel" better when Excel is in charge. I don't
think there's such a thing as a solid Excel implementation.
I'm surprised I remember this stuff. Hope it helps!
-Steven
----------------------------------------------------------------------
For information about J forums see http://www.jsoftware.com/forums.htm
