SmartSet

["Carl L. Distefano" 70154.3452@xxxxxxxx]

-> Joe Solla:
-> I had the same problem with latest version of smartset -
-> application error

Joe: I can't reproduce the problem here. Are you really loading
the latest version (i.e., SMART251.ZIP)? Its recent predecessor
(SMARTS25.ZIP) had errors which could trigger the "application error"
(but only in the case of one or two frames). Let me know,
please. If you're getting the error with SMART251.ZIP, I'll dig
further.

P.S. The problem of Ascii-37 (%) in Help-based XPL is not new to
Xy4. You'll recall that, in III+, variables in the form %n
(where n is a number) were used to read user input from fill-in
fields in certain frames. In straight XPL expressions (like "sa
%x") within, e.g., C frames, the percent sign bombed; you had to
kludge it with "BC sa R3 R7 xXC ". Your 3-byte ploy is an
interesting idea, but it doesn't work! When I command (via XPL
running under a K-frame) "sa %x" (where the "%" is a 3-byter), it writes
(instead of the expected file named "X.SAV") a file called "{255}25" (i.e,
Ascii-255 + the hex equivalent of 37 decimal, with no extension).
Moreover, what gets written to this odd-named file is not the contents of
Save/Get X, but the current file! Ditto if you specify a filename with
"sa %x,x.sav". My old III+ standby still works in a K frame.
The CMline- obliterating BC ... XC is mandatory, though; you
can't use functions within a Blind eXecute command. "BX sa R3 R7
xQ2 " bombs.

 --Carl.

--------------
Carl Distefano
70154.3452@xxxxxxxx