Business Object Interface

[dlevasseur]

So I have been playing around with doing some simple web integration using ASP.  The small scripts work well for changing basic information, but for some reason every time the script is run via the website, a pvxcom.exe process is left open on the server using 0 processor and 11mb of memory.

I took the same script and adapted it to a VBS script and all processes were killed as expected.

Is there something different about running the script from a webserver?  Every so often (15 minutes or so) the server beeps and auto kills all of the pvxcom.exe processes that seem to be dead.  I thought maybe I wasn't dropping the objects in the right order, but everything runs as expected leaving no traces when run via VBS.

hrm...

[TPeterson]

Hey Dan -

You'll need to encapsulate the BOI calls within a separate class to handle all calls to the MAS system.  Once the web site worker process launches pvxcom, it stays open until the process is killed; however, you can use that to your advantage to share one pvxcom instance across all web users that use your web site.

TP

[dlevasseur]

I still haven't been able to get this to work without leaving a bunch of PVXCom.EXE processes running.

Anyone have any examples on how to do this properly?  Someone with a working class file that I can look at and see what I'm doing wrong would be eternally grateful.