Hi Martin, I know how it feels to inherit projects and I too have decried (quite publicly) the original programmers decision on some of the strategy for those projects.
So without knowing your development environment and deployment requirement, can I suggest that you just switch to the 32-bit version of J? PROS: 1. You'll get a stable library 2. Its thoroughly tested 3. Officially supported 4. It works. CONS: 1. Nagging feeling of dissatisfaction that your using 32bit in a 64bit build 2. Can't allocate more than 1GB for each object (but why do you need to?) I been using J since version 4 and been deploying softwares that rely on J since version 5. There are some features that I feel is lacking but its a stable environment and one of my projects, an MRP for adidas apparel, is still being used this day although I've deployed it in 2003 and using J504. For the #2 CONS, I have worked around this "limitation" by partitioning my projects and a lot of forethought. Because of this, I have a capacity planning module done in J that runs on a Pentium !V 2.0Ghz with 512mb memory, the standard configuration of PC's on factory floors. The same principle hold even if my J scripts run on a big-iron compaq-hp server with 4-xeon cpu's and 6gb ram. J computes faster with smaller data to inputs ... data partitioning is key. r/Alex On Oct 14, 2010, at 9:02 PM, Martin Pelletier wrote: > This is really what I meant, J COM documentation. Incidentally, I > found some old general COM book at work, so if it comes to that, I can > explore that as well. > > I really like that I can use JEXEServer in debug mode, and JDLLServer in > release. If they really do behave the same way, that will be great. > > I also found this terrible sentence: "J64 servers have not been tested > and are not officially supported." > > I really wish my predecessors had seen this before developing with J64... > > I see that there is probably no chance of a fix with J6 now that J7 is > on its way. I don't know what I'm going to do with this. > > Thanks for all your help. > > Martin Pelletier > > On 2010-10-13 19:10, Alexander Rufon wrote: >> If you mean the J COM documentation, that can be found here: >> http://jsoftware.com/help/user/oleocx.htm >> >> If you need source code examples, I started out by looking into this >> directory >> /Applications/j602/system/examples/ole >> >> You should pay particular attention to the contents of the file: >> /Applications/j602/system/examples/ole/cpp/p_jcl/jsvr.cpp >> /Applications/j602/system/examples/ole/vb/jole.bas >> > > ---------------------------------------------------------------------- > For information about J forums see http://www.jsoftware.com/forums.htm ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
