I AM IN THE LOSTFOCUS EVENT, AND I AM CALLING A POPUP THAT IS SUPPOSED TO BE A SINGLE SELECT. THE POPUP COES UP, AND AFTER SELECTING A CUSTOMER FROM THE POPUP, THE MESSAGE I PUT AFTERWARD NEVER COMES UP. IT LOOKS LIKE THE POPUP TERMINATES THE REST OF THE PROCESS (SO I CANT ACT ON THE RESULTS FROM THE POPUP). ANYONE HAVE AN EXAMPLE OF USING REPOSTORY TO GET RESULTS FROM A POPUP?

BELOW IS THE RELEVANT PIECE OF CODE

CUS.NUMBER=Repository("EXECUTE","WEB2*POPUP**CUSTOMER","")

xxx=get_status(errcode)

MESSAGE=xxx:' ':errcode:" ":cus.number

XXX=MSG(MESSAGE,'BO','A','*')

It may just be that your message call is wrong. The official syntax for MSG in OI is different than that for AREV. Convert to the new format and see if that helps. If you are unsure of the new format put your cursor on MSG in your program and press F1.

The Sprezzatura Group

[i]Celebrate CeBIT with Sprezz Local![/i]

WE CALLED THE SAME MESSAGE WITH THE EXACT SAME SYNTAX BEFORE THE POPUP AND WE DIDN'T HAVE A PROBLEM.

Dave,

The REPOSITORY function that you have is correct. Sprezzatura's response may be the best path to take.

Here is the syntax for the MSG function in OpenInsight. There is more detail within OpenInsight Help. The first parameter of the message should not be the message structure itself but the owner window.

Description

  Displays dynamically constructed system messages.

Syntax

   variablereturn=Msg(ownerwindow, msgstructure, msgname, reserved, parameters)

Parameters

   The Msg function has the following parameters.

Parameter Description

Ownerwindow Msg requires a parent window.

           To display a message with the screen as the parent, see the Message_Box function.

           To display a message without being in event context (for example, if code is executed from the system editor) use the Windows API function MessageBox. This requires SYSTEM MODAL to be set and all string parameters to be terminated with char(0).

           An older version of Msg did not require a parent window.              This older version is still shipped with OpenInsight in order to support existing software but has been renamed as Msg2. Msg2() is automatically called if the message is displayed outside of event context.

Msgstructure

    Contains the message definition. This structure is detailed table below.  If msgname is passed, the message details that are passed in msgstructure are used to override the corresponding parts of the message definition stored in the repository.

Msgname

   To display a message stored in the repository, pass either the name of the message or the message's entity id.

Reserved

   This value is reserved; pass "".

Parameters

  An @fm-delimited list of substitutable parameter values.  Within the message text, the string "%1%" is replaced with the first substitutable parameter, "%2%" is replaced with the second, and so forth.

Sean

As far as I know, the MSG syntax you are using is outdated, but it still works–at least, I just tried it on my system and it popped up a message. If it were me, I would just put a debug statement on top of the whole thing and step through it in the debugger. See if you return from the repository call and what XXX is.

David

XXX=MSG(@Window,MESSAGE:@fm:'BO':@fm:'A':@fm:'*')

The other possibility is that the MSG call is setting the status flag and that popup is refusing to play because of this. Try adding a call Set_Status(0) before the popup call.

The Sprezzatura Group

[i]Celebrate CeBIT with Sprezz Local![/i]

View this thread on the Works forum...