Visual LANSA Forum

We have run into a rather big issue and hoping someone else may have seen this?

We have over 200 programs using the CHANGE() keyword in DDS. The indicator attached to the keyword is set on if any input field on the screen is changed resulting in the program re-validating all screen data and re-displaying that screen to the user. All of our screens are heavily modified in axes using dropdowns, checkboxes, etc... All of these screens work fine in standalone axes, and they all work fine in RAMP for VLF-Win.

These exact same screens in RAMP with VLF-One do not work. The CHANGE indicator is being set on every single time the user presses Enter on the screen whether anything was changed or not so the user can never advance past any of these screens. It seems there is something happening with RAMP in VLF-One that does not happen with RAMP in VLF-Win that is making it appear as though data is being changed on the screen every single time.

We are going to open a ticket with support to get help on this but I was really hoping someone may have already seen something like this and have an idea for resolution as this is a big roadblock.

Just updating that this may not be as widespread an issue as we first thought. Some places this is working fine and in others it is not. It seems there may be specific axes extensions causing the issue so will update if we can narrow things down.