Sign up on the Revelation Software website to have access to the most current content, and to be able to ask questions and get answers from the Revelation community

At 24 MAY 2001 04:01:52AM Simon Wilmot wrote:

I am having some problems running OI Tools using the Idleproc property. I have read previous threads and am using the following -

Declare Subroutine Set_Property

OptionStr = '/AP=?? /UN=?? /PW=??'

Cmd=!LB.EXE ":OptionStr ;* also !TMU or !DWB

Set_Property("SYSTEM", "IDLEPROC", Cmd)

When I click on the button running the above the initialisation window flashes on and then stops. If I try it a number of times I get the message 'Maximum number of queues exceeded'.

Anyone any ideas what I am missing ??

Simon

RebusHR UK


At 30 MAY 2001 12:39PM [url=http://www.sprezzatura.com" onMouseOver=window.status=Click here to visit our web site?';return(true)]The Sprezzatura Group[/url] wrote:

Are you using the ?? as the values or are you passing in a valid application, username and password?

The Sprezzatura Group

World Leaders in all things RevSoft


At 31 MAY 2001 03:33AM Simon Wilmot wrote:

The ?? are replaced by the valid values - I wouldn't expect it to work with ?? as values

Simon


At 31 MAY 2001 06:03AM [url=http://www.sprezzatura.com" onMouseOver=window.status=Click here to visit our web site?';return(true)]The Sprezzatura Group[/url] wrote:

Well, it was worth a shot on the easy answer.

Assume the same thing happens with the other tools?

Can you get this to work from a simple window?

Do you have other idleprocs running?

The Sprezzatura Group

World Leaders in all things RevSoft


At 31 MAY 2001 11:15AM Simon Wilmot wrote:

Maybe, but give me some credit

For all tools (that I have tried),

It is a simple window, a few bits on it but all it is doing is taking a selection and running a procedure to call the tool. As thing are I am using the same procedure with different lines in it until I get it working. Click Event calls procedure calls tool.

and there are not other idleprocs running with the exception of standard background indexing.

Simon

RebusHR


At 31 MAY 2001 12:00PM [url=http://www.sprezzatura.com" onMouseOver=window.status=Click here to visit our web site?';return(true)]The Sprezzatura Group[/url] wrote:

Let's try and knock this out. I took the code you pasted, placed it on a button quick event, and it loaded straight up.

I don't think IDLEPROC is the problem, but something in the load of the program.

Maybe it's a user rights problem. Can you load the tool logged in as this user? Can you load the tool from the Windows Start-]Run command line? OI will sometimes stop a user from loading tools, esp. LB, if the user rights are not correct.

The Sprezzatura Group

World Leaders in all things RevSoft


At 06 JUN 2001 10:56AM Simon Wilmot wrote:

I thought that I had responded to this somewhere, but ..

I did something like you, started with a noddy level window with a big button that ran the code and it worked OK. I changed some bits to get the window called where I wanted it and it still worked.

So I copied the bits and pieces from the original window into my new one bit by bit, and then event by event testing as I went, and it carried on working. I have completed the window and it still works - there is no obvious difference between the windows !!

So I don't know, but my problem has gone away ….

Simon

RebusHR


At 18 JUL 2001 05:40AM Simon Wilmot wrote:

but ….

I am sure I had it all working before, but now, System Editor works fine, but both Database Manager and Table Builder do what they did originally - flash up and disappear, but do seem to be held in a queue as when you close down the engine reports that processes are running.

I use identical code apart from the exe names - anyone any ideas ??

Simon

RebusHR


At 18 JUL 2001 06:50AM [url=http://www.sprezzatura.com" onMouseOver=window.status=Click here to visit our web site?';return(true)]The Sprezzatura Group[/url] wrote:

Simon

We believe your code is probably right. Here's a code snippet from the forthcoming S/List for AREV that does what you are describing…

Case Param1 = "DATABASE"

Cmd=!LB.EXE /AP=: @appid: " /UN=: @username

DataArray = Set_Property("SYSTEM", "IDLEPROC", Cmd)

The Sprezzatura Group

World Leaders in all things RevSoft


At 18 JUL 2001 09:42AM Simon Wilmot wrote:

That is basically it with /PW=password tagged on the end.

Why then should it work for System Editor, but not the other two ??

Simon

RebusHR


At 18 JUL 2001 10:29AM [url=http://www.sprezzatura.com" onMouseOver=window.status=Click here to visit our web site?';return(true)]The Sprezzatura Group[/url] wrote:

Do you have anything else open? Try it with just bare bones OI, no system monitor, no outlook etc etc.

The Sprezzatura Group

World Leaders in all things RevSoft


At 18 JUL 2001 10:41AM Simon Wilmot wrote:

I've done that - when I noticed it had 'regressed', I rebooted the PC and ran just the part of the system that it was using.

The difference from before is that I couldn't get any of them to run. I need it to run from within the system with the parent window open, but that it all there is ..

Are there any system settings that I may be setting inadvertently that will cause the Database Manager and Table Builder to fail when System Editor doesn't ??

Simon

RebusHR


At 23 JUL 2001 04:41AM Simon Wilmot wrote:

Something that may be a pointer ??

I have just started another new window to prove that it still works properly like that. Changed the calling procedure slightly so it runs from my development area and on the Database Manager the window header included 'SYSPROG' instead of my App Id. Checked running from OI menu and OK there.

Is there a problem with calling Database Manager from IdleProc and not from Sysprog ??? (and Table Builder ??)

Simon

RebusHR

View this thread on the forum...

  • third_party_content/community/commentary/forums_nonworks/ff61b898ce39555385256a56002c1e0c.txt
  • Last modified: 2023/12/28 07:40
  • by 127.0.0.1