Wow, that was a fast response, I was changing the programming and deleted the original message!

So, any hints as to how I can identify @userid when I first enter a form? I was going to put the programming into an element, but a user may not enter thta element in search mode.

I guess I'm missing something.

I put an unbound static text element on the form: LE42
It is not labeled. Programming is:

var vWho as String

vWho = @UserID

if vWho = "fberg" then
{
  LE42 = "fberg"
}

I log on as fberg, and the element is blank when I open the form. I guess I'm not understanding why I should use a static text element to hold a changing variable.

Maybe I need to reboot and start over.

Here's what I have.
Static text element LE42 unlabeled. Width 135, Height 18
Form name: Orders
On form entry (Orders):
Le42 = @UserID
ForceRedraw()

Logged on as: fberg
Preview app: Le42=""

Don't "ASSUME" anything. 

Isn't amazing how sometimes missing ONE little step makes a big difference? Talk about a rookie mistake.

Thanks for your time, effort and PATIENCE with me!!

Thanks Mark, that's exactly what I was looking for. Even the Loiter works well now.
When I grow up I wanna be just like you! LOL (celebrating 35th wedding anniversary today)

Thanks for the thought!

Re: Loiter - I actually wanted a WriteLn box to inform the user who they are logged on as, then disappear. I don't really need the info as part of a permanent record. We have a couple of users that need to log on differently depending on what they want to do.

Now this leads to another question. Is it possible to do an @MSGBOX in SEARCH mode, not UPDATE? I'd like to prompt the user how to enter retrieve criteria, i.e., ("Do not enter data with dashes.","USE: 5400PC192 vs 5400-PC-192","").

The next morning: Re-reading this, I wasn't clear enough. I know I can do an @MSGBOX "On Retrieve Spec Open" because I"m doing it. What I'm after is to do another box when a PO# field is entered to input retrieval criteria. I wouldn't want the box to pop up every time the form was entered because the person may not be doing anything with the PO# - that would just be annoying.

I thought about that, but I just don't have room on the Form for another element. It's something needed by only a few people, so I don't want it appearing every time I open the form.

I also thought about using a mask, but that won't work as the order number grows (999-1000, etc). I'll keep gnawing away. I guess once the people that are using that portion of the report get a little experience, it really won't be needed anyway.

Thanks for the idea!
Fred