artjuh
14th November 2002, 13:58
Baan Version: B40c4
Unix platform: Sun Solaris
Database Backend: TRITION
What i'm doing:
i'm changing the way of a layout of a report.
How ? :
session: ttadv3130m000
Press Layouts
Press Ctrl+Shift+D
(or Special+mutate all layouts coll.)
Problem:
everytime i switch between an layout (before.field, detail, after.field) the editor ask me to save changes. even if i made none.
Does someone know's if i can change a default that it won't ask me anymore ?
Greetz,
Artjuh
OmeLuuk
14th November 2002, 15:59
How do you (s)witch between layouts?
(added s)
artjuh
14th November 2002, 16:34
I think you tried to type Switch but okee ;)
i just switch between layout's with my mouse
i have that whole report for me en then you can go from mlayout to layout but i also tried it with the PgDn-Key and i still get the message if i want to save the modifications.
Groeten van Ome art ;)
evertsen
14th November 2002, 16:43
This is not typical behavior as far as I know. I have seen this posted before with no answer Disable prompt (http://www.baanboard.com/baanboard/showthread.php?s=&threadid=5357&highlight=save+layout). I suspect you'll have to wait until Baan Support comes up with a fix. You should log a case with them if you haven't already.
tools123
14th November 2002, 19:29
I have experienced the same on 4c4.
on 4 c2 the editor is just fine.
May be this is intentional feature so as to save all the
work done just in case...???
evertsen
14th November 2002, 19:51
I'm on 4c4 as well but have never experienced this. Perhaps it's a bug in a specific patch or SP? You could try installing the latest solution for ttadv3130m000.
ltannous
14th November 2002, 23:27
We were on service pk 6 and now we are service pk 11. One of them created this "new" functionallity, which I also do not care for.
Eddie Monster
15th November 2002, 13:48
I don't think that it's SP-11. We're currently on 10 and have that 'functionality'. I also hope there is a way to disable it.
themeus
15th November 2002, 14:55
We are running BaanIVc4 and there is no problem you described (probably of the low service pack reason) but if you install solution number 121558 it "repairs" editor that it works as you described. Check on that solution.
On BaanVc that problem is present as well, but I don't know what solution is responsible for that (if any) So if anyone knows help, help...:(
ltannous
19th November 2002, 03:27
I think that is the problem. Is there a solution out there to get rid of this saving prompt?
evertsen
19th November 2002, 03:41
Looks like the only way is to uninstall 121558.
ltannous
19th November 2002, 03:56
That should do it I hope
ltannous
19th November 2002, 15:57
The patch(for us) was installed in the tools service pk 10, and wont let me uninstall using pmc
evertsen
19th November 2002, 20:38
I was afraid of that. You would have to uninstall the entire service pack.:( Then either, just go with SP9 or reinstall all the SP10 patches individually without 121558.
What I would suggest as an alternative to this is to replace your editor object (ottadvformedit) with an older version.
ltannous
20th November 2002, 04:36
I think I will try that. It should work.
OmeLuuk
20th November 2002, 09:30
One of my customers is facing the same problem, I will try to have it solved by a new solutions (if not done yet)... I will keep you posted.
On reproduction: the error does not come when clicking or switching between layouts when you click on the black space.
When you double click on a field (subsession opens) or when you click and move your mouse over a field (even too little to actually move, but enough to put + on field limits) then the question will come.
It seems currently it will only happen when you enter edit mode. Even without actual changes.
Log a case and have your cases being linked to defect 131143.
OmeLuuk
28th November 2002, 18:34
The "end" of the story was: artjuh was this one customer of mine and Baan is not willing to change things.
And we had to be more precise in the problem definition: the question pops up whenever you enter a subsession or perfrom an action that can also be seen as an edit action. Like open a field dialog to view it's contents (where you could also have changed it) and move a field (even if it is only too small distance to have actually moved it, but you was ++ at each side) etc.
Currently the check is: whenever you were in edit mode, the editor assumes you could have made changes that were to be confirmed.
The fact that it worked without questions in the past was an error: it was also not saved when you did actually make changes. In that case this is better than not saving any changes at all...