Data Type boi com connections

I'm planning on creating a data type of boi connections for performance reasons.

Currently my application adds parts to each company (we have four).  The application spends

too much time opening and closing sessions, objects etc.

My plan is to create a type similar to below:

Type boi_com

dim session as object

dim script as object

module as object

...etc

then initialize all connection when the program starts, and truly impress my friends!

Anyone play with boi this way? Advice?

BS

  • 0

    Hi Sevendogzero,

    Sounds like a fun project!

    My recommendation would be to implement the dispose pattern, and to call the SY_Session.nCleanup() method in your dispose method, as well as to dispose the Pvx Script object itself. You can tell when these two things are working when after your application launches and closes several times, there are no orphaned pvxcom.exe processes left running, and SY_Workstation.M4T is not collecting orphaned records.

    Thanks and hope that helps!
    Bret

  • 0 in reply to Bret

    Made the changes. Happy users.

    Regarding the boi calls. I check the master console for evidence of my routines running. How would I look in the SY_WORKSTATION table (or is the same thing)?

    Awesome name by the way (that's my name also).

    Thanks, Bret

  • 0 in reply to sevendogzero

    Hey cool! And spelled the same too...

    You can use DFDM (the data file display and Maintenance) utility in Sage 100 to view the SY_Workstation.M4T records. There will always be some records in there for currently running sessions and tasks. But what you are looking for is if any records that are created by your BOI app are getting left out there.