apl+win runtime

Comments:

Author Thread:

Patrick.Parks

apl+win runtime
Posted: Wednesday, June 07, 2006 6:17 PM (EST)

If you rename the aplwCo.dll as vipillCo.dll and register it again with regsrv32, then things should start working for you again. That aplwCo.dll must match the name of the aplw.exe file with with Co added. So if you are running myapl.exe you need to have the DLL named myaplCo.dll. You also mentioned aspx20ocx.dll but that was probably a typo... I think you must have meant apx20ocx.dll. Otherwise, that could be another problem.


EcklerDev

apl+win runtime
Posted: Thursday, June 08, 2006 3:33 PM (EST)

I did rename the "aplwCO.dll" to "VIPILLCo.dll" and re-registered it. I got the same message: "ActiveX component can't create object".

There is my code in VB:

Dim ws As Object
Sub Auto_Open()

    loadAPL
End Sub
Sub Auto_Close()

    closeAPL
End Sub
Sub loadAPL()

    Set ws = CreateObject("APLW.WSEngine") '<------it crashed here
    wsPath = Application.ActiveWorkbook.Path
    workspace = "load " + wsPath + "\VIPILL"
    ws.SysCommand workspace
End Sub
Sub closeAPL()
    Set ws = Nothing
End Sub
Sub runVIP()
   Dim ans As Variant

   ans = ws.call("RUNAPL")

   Set ws = Nothing

End Sub

All the files are saved under the same directory and registered.

I followed all the instructions provided by APL2000 to produce an ActiveX component. Is there a specific way to create this that is not mentionned in the guide?



Support

apl+win runtime
Posted: Thursday, June 08, 2006 4:30 PM (EST)

Your initial attempt at registering vipill.exe should've failed to register the executable because vipillco.dll wasn't present. Now that vipillco.dll has been successfully registered, you will need to re-register the vipill.exe before it can be created.

APL2000 Support


EcklerDev

apl+win runtime
Posted: Thursday, June 08, 2006 5:04 PM (EST)

I re-registered the "vipill.exe" using C:vip\vipill.exe \regserver. How should I know if it was registered correctly? Should I get a message telling me that it was registered successfully? When I registered the vipillCo.dll, I got a message but not after the ".exe"


Patrick.Parks

apl+win runtime
Posted: Thursday, June 08, 2006 5:56 PM (EST)

Your message above shows the option as \regserver. That slash is backward. It should be /regserver. But in any case, running the command does NOT display a message. However, you can verify successful installation after running the registration command by starting the APL development system running and executing the express: '#' QuadWI 'XInfo' 'APLW.WSEngine'. It should produce two lines of output saying something about "APLW.WSEngine" and "APLW.WSEngine.3". If that works, then APLW.WSEngine is registered and you should be ready to run. Then I would suggest you try creating an instance of the APLW.WSEngine from APL by executing the expression: 'ws' QuadWI 'Create' 'APLW.WSEngine'. If that works without returning an error, then trying loading your workspace and making the call from APL by executing the expressions such as: 'ws' QuadWI 'load ',wsname -AND- 'ws' QuadWI 'call' ...


Support

apl+win runtime
Posted: Thursday, June 08, 2006 11:10 PM (EST)

Following up on Patrick's reply, the command "C:vip\vipill.exe \regserver" doesn't register the interpreter but instead causes vipill.exe to run and load a workspace named "regserver.w3" in C:\. And because vipill.exe is a runtime interpreter and therefore has no visible window, you won't see the "WS NOT FOUND" error message normally displayed in the session. Properly registering vipill.exe with /regserver should solve your problem.

APL2000 Support