Unusual DATA problem

[Tom Pellitieri]

I ran into a problem with a fairly standard process that I thought I should share.

We have a screen that lists new user names for update in a MV field.  When you highlight the name and press F5, it calls a process to DATA the name as the key for the maintenance screen.  Effectively, the /PD.P has this code:

LOCAL NEW.USER
NEW.USER = @RECORD<1,@CNT>
DATA NEW.USER
EXEC "I*USERS*MAINT"

Today, one new name just wouldn't go in.  It turns out that the problem was with the data.  The name was formatted as "myname@1400"

I determined that the problem was the "@14" - it appears that SB+ translated this to an Edit key.  Since @14 is the code for Escape, the maintenance screen just quit before any work could be done.  I was able to manually enter the item, but the DATA statement really didn't work well at all.


--Tom

[precisonline]

Wow.  I've never seen that before but you're right, the @ probably got interpreted by SB+.  Did you try generating code for the screen to see how the @ signs are handled in data stacks?