| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 3471.1 | Narrow down the problem | UTRTSC::SMEETS | Martin, CSC Office support (NL) | Fri Oct 29 1993 13:07 | 17 |
| Hi,
I'm able to reproduce the behaviour on our production V3.0-1 system.
I'm also able to narrow down the problem.
Create an UDP with name F17.UDP; contents of this UDP "."
Access form EMC by FORM EMC/CAPTIVE
1. Press F17, nothing happens, remain in form EMC
2. Press DO or GOLD-U and execute F17.UDP result error message and I'm back
on the MAIN form
Martin
|
| 3471.2 | Application into production, fix needed | UTRTSC::SMEETS | Martin, CSC Office support (NL) | Tue Nov 02 1993 08:20 | 8 |
| Hi,
My customer is going to take the application into production and would like to
know if there will be soon a fix for the problem !
Thanks,
Martin
|
| 3471.3 | Define "." and ".." on the form? | IOSG::PYE | Graham - ALL-IN-1 Sorcerer's Apprentice | Tue Nov 02 1993 10:11 | 9 |
| You might want to search through this or the older conferences, but I
seem to recall this was worked round before by defining "." and ".." as
keystrokes to do OA$NULL or similar on the captive form. I don't know
if you can put the definitions in DEFAULT or a .MORE so they work for
all forms.
Does un-setting any of the PRVUPDxxx flags have any effect?
Graham
|
| 3471.4 | Doesn't work ... | UTRTSC::SMEETS | Martin, CSC Office support (NL) | Tue Nov 02 1993 11:16 | 21 |
| Hi Graham,
> You might want to search through this or the older conferences, but I
> seem to recall this was worked round before by defining "." and ".." as
> keystrokes to do OA$NULL or similar on the captive form. I don't know
> if you can put the definitions in DEFAULT or a .MORE so they work for
> all forms.
I did define the following in the captive form
;;.;;
OA$NULL
Result: same behaviour e.g. fld_exit and error message
> Does un-setting any of the PRVUPDxxx flags have any effect?
By default these user's only have XOWN privilege
Martin
|
| 3471.5 | Take away XOWN? | SCOTTC::MARSHALL | Spitfire Drivers Do It Topless | Tue Nov 02 1993 12:04 | 9 |
| >> by default these users only have XOWN.
If the management at this site are so paranoid that they don't want their users
getting out to the main form, then they probably shouldn't let them have XOWN
either! Any UDPs, etc, the users need to access should be in the system (site)
areas and maintained by the system manager who can then ensure they don't
contain "." or anything else that causes problems.
Scott
|
| 3471.6 | I fully agree, but we need customers.. | UTRTSC::SMEETS | Martin, CSC Office support (NL) | Tue Nov 02 1993 13:06 | 19 |
| Hi Scott,
> If the management at this site are so paranoid that they don't want their users
> getting out to the main form, then they probably shouldn't let them have XOWN
> either! Any UDPs, etc, the users need to access should be in the system (site)
> areas and maintained by the system manager who can then ensure they don't
> contain "." or anything else that causes problems.
I fully agree ......
On one hand this site wants to restrict the use of ALL-IN-1 to this specific
application on the other hand they allow users to create and execute UDP's...
We (Digital) have to face that this is the way the customer uses ALL-IN-1 and
reasonable or not the customer runs into a problem (bug?) which according to
the documentation shouldn't be a problem at all.
so, how do we continue ?
Martin
|
| 3471.7 | It will be looked at | IOSG::DUTT | Nigel Dutt | Tue Nov 02 1993 14:05 | 3 |
| Martin,
I reported the problem internally, so it will be reviewed.
|
| 3471.8 | Memory fading.... | IOSG::PYE | Graham - ALL-IN-1 Sorcerer's Apprentice | Thu Nov 04 1993 17:35 | 5 |
| Re .4
Strange, I'm sure I remembered someone describing a way to trap those.
Graham
|