Aurokripa
asked on
Problem with DISP.
Hi experts,
We are facing really critical and fuzzy problem,
We are using Lotus Notes 4.6.1(Domino Intranet Starter Pack 2.0) on NT Server to develop one Browser based system. Problem which we are facing just now is because of Index (as per our thinking).
Problem: We are makeing one form say 'Employee Registration Form' to feed data, and using one view say 'Employee View' to the entered data. Addition of records with above form through browser is used to manage other forms of the system also. After some time suddenly(it might be magic) if we change the value of one field in one of the existing documents from browser, then it changes and also shows when we second time view it from browser, but when we open the view in the Lotus Client(Designer client) the value isn't changed, and the beauty is when we goes in the design of that view the change is visible. Now we some how manage to solve above bug also, to solve the above bug add space in the formula of any column of the view and delete the space(actually by doing so we don't change anything in the design part of the view) and close the view, at that time Notes asks you to save the changes made, we press yes and the value is now change in the view also.
I think that it's a bug of DISP 2.0, because the same problem, with same solution you can face when you install the Domino Server from the DISP 2.0, when you Register multiple person some time the Register person is not displayed in the person view of Names and Address Book(names.nsf), and when you change some part in the design mode of view and save it the problem is solved.
Now we want to manage the above solution from Browser. Is the problem occurs because of Indexing? Please give us some solution to overcome the above bug from runtime not from the designtime. We also want some solution to delete index and create index at runtime( we don't want to use UpdateFTIndex), can there be some solution?
Waiting for your quick and positive reply with regards,
-Nilesh Shah.
We are facing really critical and fuzzy problem,
We are using Lotus Notes 4.6.1(Domino Intranet Starter Pack 2.0) on NT Server to develop one Browser based system. Problem which we are facing just now is because of Index (as per our thinking).
Problem: We are makeing one form say 'Employee Registration Form' to feed data, and using one view say 'Employee View' to the entered data. Addition of records with above form through browser is used to manage other forms of the system also. After some time suddenly(it might be magic) if we change the value of one field in one of the existing documents from browser, then it changes and also shows when we second time view it from browser, but when we open the view in the Lotus Client(Designer client) the value isn't changed, and the beauty is when we goes in the design of that view the change is visible. Now we some how manage to solve above bug also, to solve the above bug add space in the formula of any column of the view and delete the space(actually by doing so we don't change anything in the design part of the view) and close the view, at that time Notes asks you to save the changes made, we press yes and the value is now change in the view also.
I think that it's a bug of DISP 2.0, because the same problem, with same solution you can face when you install the Domino Server from the DISP 2.0, when you Register multiple person some time the Register person is not displayed in the person view of Names and Address Book(names.nsf), and when you change some part in the design mode of view and save it the problem is solved.
Now we want to manage the above solution from Browser. Is the problem occurs because of Indexing? Please give us some solution to overcome the above bug from runtime not from the designtime. We also want some solution to delete index and create index at runtime( we don't want to use UpdateFTIndex), can there be some solution?
Waiting for your quick and positive reply with regards,
-Nilesh Shah.
When ever you have a dynamic view, where people try to interact and change values, Index of the view should be so neat that once the documents is seen in the view, it shows beautiful, data only.
In LN, there is always a law, Do it right the first time. If you create a column with some formula, and after some time change many values to the column, the view might get corrupt, It is not always, but sometime.
Solution:
Create a Action button, which can refresh to the field level.In the formula for action button use @command([ToolsRefreshallD
IF not
try using reindexing and refreshing the view by pressing Ctrl+F9 for the current view, and for all view use Ctrl+Shift+F9.
This could solve most of your problem.
In LN, there is always a law, Do it right the first time. If you create a column with some formula, and after some time change many values to the column, the view might get corrupt, It is not always, but sometime.
Solution:
Create a Action button, which can refresh to the field level.In the formula for action button use @command([ToolsRefreshallD
IF not
try using reindexing and refreshing the view by pressing Ctrl+F9 for the current view, and for all view use Ctrl+Shift+F9.
This could solve most of your problem.
Aurokripa,
When a field is updated in a document the change in the field value is immediately reflected if
1. In the form properties, Defaults tab, 'Automatically refresh fields ' is enabled
2. In the view properties, Options tab, On refresh list is set to the relevant choice
3. Whenever the update is done programatically, use relevant method (eg: viewRefresh method in the NotesUIworkspace class) to refresh the view. This will certainly help. or use @commands
SathyaCSSNarayana,
Do it right the first time applies to everything in life :)) not just Notes! I dont think views get corrupted due to change in column or selection formula.
When a field is updated in a document the change in the field value is immediately reflected if
1. In the form properties, Defaults tab, 'Automatically refresh fields ' is enabled
2. In the view properties, Options tab, On refresh list is set to the relevant choice
3. Whenever the update is done programatically, use relevant method (eg: viewRefresh method in the NotesUIworkspace class) to refresh the view. This will certainly help. or use @commands
SathyaCSSNarayana,
Do it right the first time applies to everything in life :)) not just Notes! I dont think views get corrupted due to change in column or selection formula.
Hi All,
I did face the same problem sometime ago. Aurokripa, delete the view and recreate another one. It is corrupted.
Dont try and copy this view or modify this view. Discard it totally.
:)
Arun
I did face the same problem sometime ago. Aurokripa, delete the view and recreate another one. It is corrupted.
Dont try and copy this view or modify this view. Discard it totally.
:)
Arun
ASKER
Hi all experts,
I am surprised that none of you is getting my point !!! I am developing a browser based application where
1. Desinged is not with the user
2. Application is browser based so notesUIworkspace class can not apply.
3. Some or how index is currepted, and user don't have any Notes Client.
4. I wanted to give some option on my browser only where admin user can delete an index and able to create.
I hope you have understood my problem and I expect an answer with code or example.
Thanks a lot to everybody who have taken good interest with my problem.
Regards,
Nilesh
I am surprised that none of you is getting my point !!! I am developing a browser based application where
1. Desinged is not with the user
2. Application is browser based so notesUIworkspace class can not apply.
3. Some or how index is currepted, and user don't have any Notes Client.
4. I wanted to give some option on my browser only where admin user can delete an index and able to create.
I hope you have understood my problem and I expect an answer with code or example.
Thanks a lot to everybody who have taken good interest with my problem.
Regards,
Nilesh
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
In LN, there is always a law, Do it right the first time. If you create a column with some formula, and after some time change many values to the column, the view might get corrupt, It is not always, but sometime.
Solution:
Create a Action button, which can refresh to the field level.In the formula for action button use @command([ToolsRefreshallD
IF not
try using reindexing and refreshing the view by pressing Ctrl+F9 for the current view, and for all view use Ctrl+Shift+F9.
This could solve most of your problem.