I have two OI runtimes.

Runtime A,

Runtime B.

Using Runtime B, I want to know how many users are logined into Runtime A.

I tried attaching SYSLOGINS from Runtime A into Runtime B.

But I found out that SYSLOGINS from Runtime A does not update unless Runtime A is running. But I require the Runtime B to run WITHOUT running Runtime A.

Meaning, when Runtime A is off, its SYSLOGINS still shows the last login users, when Runtime A is runned, then it will only be updated.

I want the Runtime B to detect no users are logined into Runtime A when no runtime A is runned.

All helps are appreciated. Thanks in Advanced.

If runtime A isn't running, then won't the answer be zero?

You're really asking for technical details on how many users are logged into any one system, and how this is monitored by the exe in terms of licensing.

Is this for implementing a backup strategy?

What's the real business problem here?

Thank you for the responding,

Yes, this is for implementing a backup strategy.

What I meant was that

Runtime A's SYSLOGINS will always keep track of the

last users that has login to it, unless the system

was reboot and no one has login to Runtime A before

since the reboot.

SYSLOGINS somehow only updates its table when a new

user login to the Runtime. And not during the logout

of its previous user.

The runtime A runs in a network environment where

multiple users access the runtime A through a

server where all Runtime A's files is stored.

The server should be running most of the time and

one or more user(s) might be using it at the same

time most of the time.

I am trying to detect that while there are user using

Runtime A, the backup module Runtime B will not

initiate backup until all users have logout and closed

Runtime A.

Thank you for your assistance.

Jonathan,

The update of SYSUSERS is controlled by SYSLOGINS.MFS

I think you could log a user into engine 'A' from Engine B using CreateEngine, CreateQueue and CallFunction. There is a section in the help file on the openengine that can get you started.

or

A simple strategy would be to rename oengine.dll.

If Oinsight is in use you will not be able to rename it.

You could use OLE with the Scripting.filesystemObject to program this.

- Bob

If this is for a backup strategy then you could try deleting the REVLOCKS file from the OpenInsight directory.

E.G.

OSDELETE "pathtoOpenInsightDirectory\REVLOCKS"

errCode=status()

if errCode=0 then

// no one is logged in

end else

someone is logged in end Dave G </QUOTE> View this thread on the forum...