You may also try calling j.dll directly without com,
http://www.jsoftware.com/jwiki/Scripts/CallJ
I think this is the way to go unless you are actually interested in com
itself.
Втр, 28 Дек 2010, Steven Taylor писал(а):
> "Did you find you had to a manual registry update.?I think regsvr32 j.dll
> would do the required. If you tried that and it didn't work I would like to
> know. Thanks for pursing this."
>
> Hi Eric,
>
> I tried regsvr32 early on, but it had no effect. Normally this is the
> cure-all for COM, but not this time.
>
> I hunted around the microsoft site + chased down various leads... one of
> which was to ensure .net was being compiled to 32 bit. This was already the
> case. Another suggestion was the COM/COM+ security settings for Win7 64...
> again, setting were in order, and even upgrading security for the J
> component had no effect.
>
> So from there, I decided to stay with j602 64 bit for now. As I couldn't
> use the .dll anymore, one of the suggestions on the J forum from January
> (from Oleg?) was to use the Exe instead. Did this, and everything seemed to
> be fine. I could push data in, but when pulling it out again, the results
> are garbled up. i.e. the pattern initially looks a little like unicode might
> e.g. {number} 0 {another number} 0 ... etc ... until there is no resemblence
> at all -- this is an impression as the returned array had hundreds of
> elements... perhap my results were wrong... but it looks like memory not
> being translated correctly.
>
> So, I alternated between the .GetB() / .Get() methods to retrieve data, and
> I was not relying on the text results comming out of DoR.
>
> So, I then confirmed that the data transport mechanism is suspect (at least
> here) with some natively generated J data using "ret=:50-i.100". These
> later tests done on j602.
>
> I'm fairly sure that that j.dll was returning the right results when it was
> still working on my machine.
>
> Hope isn't normally a good remedy, but I am hoping that I can get this
> going.
>
> No problem on following this up. I wasn't sure if I was being a pest or not
> by asking about stuff you guys might be trying to retire.
>
> Tomorrow, I guess I'll start testing with j602 32 bit / j7 32 bit. That
> shouldn't be a problem given the the data sets are reasonably sized.
>
> thanks,
> -Steven
> ----------------------------------------------------------------------
> For information about J forums see http://www.jsoftware.com/forums.htm
--
regards,
====================================================
GPG key 1024D/4434BAB3 2008-08-24
gpg --keyserver subkeys.pgp.net --recv-keys 4434BAB3
----------------------------------------------------------------------
For information about J forums see http://www.jsoftware.com/forums.htm
