If I make a change, particular when changing views, if I then save and test in the client the changes just are not saving.
The only way to save is to close the view and then re-open it and do the changes again.
The first time this happened I just thought I had forgot to save the changes before testing and then the second time I just thought I was having a bad day. But this is happening all the time and not just when changing views.
I added 3 lines of script to the QuerySave event and only two lines were saved and the middle line was missing!
This is really worrying as I never know what has actually been saved and I have to do additional testing.
If anyone is having the same problem I would be glad to hear its not just me and if anyone knows why and how to the solve the problem I would be over the moon.
Please please if anyone has any suggestions or anything I would be grateful!!!
Subject: Help! Saving the database design changes isn’t actually saving…!
I’m having the same problem. But it doesn’t occurs very often.Then I must to close the design element, and re-open it. I lose the unsaved data, of course.
My users are having a similar problem after upgrading to 6.0.1. They edit a document in an application. Save the changes and close the doc and no changes are made to the document. Is intermittant fot two users only - Any ideas?
I have found that when I leave a design element open in the designer client and switch to the Notes client to test. When I switch back to the designer client and make additional changes, those additional changes do not save. If I close the design element, I do not have this problem. Also, this problem seems to only happen when I create a new design element like an agent or a view, etc.
I think that you have the problem of disappearing LotusScript that has been discussed elsewhere in this forum. It is maddening when it happens. At times I have been forced to go back to R5 to do my coding.