I have version 3.12 of Advanced Revelation, and 3 applications with several users in Novell environment, each user may access to the applications via 3 different icons in windows 3.1 or via DOS prompt. What can I do to prevent or block next?

a.- that a user no access twice or more than one to the SAME application.

b.- that a user no access to different applications at the same time, only to one application.

Whole this, beause each time that a user accesses, requires for a lanpack license.

Please, let me know if there is a solution about this.

Thank You.

Victor,

You can lock a record with the user's Novell ID in it. If he logs on and it is locked already then you can log him out. There is a utility to get the Novell user ID on my web page at http://www.ozemail.com.au/~stsm/

Another way is to set a DOS environment variable=login ID from his Novell login script, then read the DOS environment to get the ID.

You could also lock a record key=@station from the AREV logon script.

Steve

I have heard of someone somewhere that wrote a Visual Basic program which would be run as part of the PIF. The program runs first and checks to see if AREV.EXE is already running. If it is then it will not let you launch another instance of AREV.

As far as the previous solution goes that will work. But if you use NT I am am not sure about the @STATION variable.

You may want to write an RBASIC program that checks for the user AREV login name and and check it against and AREV file that contains a list of who is logged in.

Bob

LYNCHRW@EROLS.COM

BOB_LYNCH@ADPBENEFITS.COM

If you use the @STATION idea, make sure you're using the second part if it's a multi-part station. Starting with ARev 2.1, @STATION is prefixed with a running counter to allow for unique station ids when running multiple copies.

apk@sprezzatura.com

Sprezzatura, Inc.

Thanks for your answers.

I tried with lock a record key=field(@station,'*',2) and the

results was succesful.

Best regards, VB

Actually, it's quite easy.

Just insert this code into your logon program or write a new program and put it first in your logon verb.

call VIDEO.RW( 0, 0, (@crtwide-1), 1, "R", TopLine )

pcperform 'MEM /C ] TESTX'

OSREAD Test from 'TESTX' then

 OSDELETE 'TESTX'

 if INDEX(Test,'AREV',2) then

    mssg=|You are trying to log in on top of an already running system.||'

    mssg := 'You will now be logged off.||'

    mssg := 'After the logoff, you should type "EXIT" to resume the running system.|'

    call msg(mssg)

    execute 'OFF'

 end

end

call VIDEO.RW( 0, 0, (@crtwide-1), 1, "W", TopLine)

As far as I know, this works for all DOS from 3.3 thru WindowsNT 4.0 Server. Please let me know if this works for you, and if not, what version of Revelation, DOS, Netware, etc. you are using.

Larry Wilson

tardis@earthlink.net

http://home.earthlink.net/~tardis

303-432-8630

Larry,

I just did the following in the order given:

1) Log in to Arev.

2) Click on the DOS prompt.

3) MEM/C

Arev does NOT appear in the listing. This is on Windows 95. I don't know if this makes a difference, but the shortcut is set up with "Prevent MS-DOS based programs from detecting Windows" checked.

Larry's script wil work, but you need to be careful if you are running an NLM that is unloaded upon completion of the session. Unless you have properly loaded the TSR for each independent session, you may end up causing a shutdown of your initial REV session.

View this thread on the forum...