Well, now with DDE 8.5 FP1, I can do this again.  Woot!

• Teamstudio Profiler
• BinaryTree's CMT Inspector
• Technovations GroupSizr

At my current company, this technique was used in several high-profile applications.  It seemed to work fine until we migrated to Notes 6.5 in 2005.  Now, users call us occassionally stating that rich text fields that were being hidden or displayed via the pseudo-tabs are now either appearing when they shouldn't be, or are disappearing alltogether.

All I want to do at this point is replace the pseudo-tabs with regular tabbed tables.  Unfortunately, the rich text fields where the hide/when formulas are out-of-whack won't magically reappear in the tabbed table.

From what I can see in the Domino Object Model, there doesn't appear to be a way to clear out hide/when formulas in rich text fields.  Has anyone out there found a way to programmatically clear hide/when formulas in existing rich text fields?

Dim s As NotesSession
Dim db As NotesDatabase
Dim v As NotesView
Dim doc As NotesDocument
	
Set s = New NotesSession
Set db = s.CurrentDatabase
Set v = db.GetView ( "($All)" )
Set doc = v.GetFirstDocument
	
Forall v In doc.Field1
	'-- Do something here
End Forall
	
Forall v In doc.Field2
	'-- Do something here
End Forall

Whether the view is collapsed entirely on open is dependent on which document was highlighted when the view was closed. If a Main document or highest level document in a hierarchy is highlighted when the database is closed, then all categories will be collapsed when the view is opened. If a response or child document is highlighted when the view is closed then that discussion thread will be expanded when the view is opened, but all other discussion threads in the view will be collapsed. A discussion thread is a collection of documents that all have the same Main Document ancestor, ultimately.

ap := @DbLookup ( "Notes" : "NoCache"; svr : path3; "someview"; @Name ( [CN]; @UserName ); "Approver"; [FailSilent] );
isMCApprover := @If ( @IsMember ( "[MC]"; @UserRoles ); @True; @False );
isAPApprover := @If ( @IsMember ( "[AP]"; @UserRoles ); @True; @False );
@SetTargetFrame ( "_top" );
@Command ( [OpenFrameset]; "Main Frameset" );
@SetTargetFrame ( "NotesView" );
@If (
@Name ( [Abbreviate]; @UserName ) = ap | isMCApprover;
@Command ( [OpenView]; "AllToBeApproved" );
isAPApprover;
@Command ( [OpenView]; "APtobeprocessed" );
@Command ( [Compose]; "SelectEmpStatus" )
);

@If ( @Version > "147"; 
@PostedCommand ( [OpenNavigator]; "Main Navigator 6.5"; "1" ); 
@PostedCommand ( [OpenNavigator]; "Main Navigator"; "1" ) )

1. I can test my design changes in a development database that inherits its design from the new template while the production database inherits its design from the current template. Sure, you can accomplish this without using templates, but unless you're making your changes to the live production database (a big no-no), you'll have to designate your dev db as a template and use it to refresh the design of the prod db. But if you do that and something goes wrong, how will you restore the prod db to its original design? If the problem is urgent, who has time to wait for the db to be restored from a backup tape? And what if a good backup doesn't exist?
2. I can make changes to a local replica of the template, instead of a local copy of the production database. This is very useful if the production database is several hundred mg, and I don't want to waste time making a local replica.
3. When it comes time to move the changes into production, all I need to do is change the design template name of the production database and let the Designer task make the changes for me overnight.
4. Opening a template with no documents is much faster than opening a local or server based replica of the actual production database.
5. Comparing design changes between templates using a product like TeamStudio Delta is a snap.

If ( profile.IsNewNote ) Then

Dim w As NotesUIWorkspace
Dim currUIdoc As NotesUIDocument
Dim currDoc As NotesDocument
Dim s As NotesSession
Dim db As NotesDatabase
Dim newDoc As NotesDocument
Dim newUIDoc As NotesUIDocument
Dim parentDoc As NotesDocument
	
Set w = New NotesUIWorkspace
Set currUIdoc = w.CurrentDocument
Set currDoc = currUIdoc.Document
	
currUIdoc.AutoReload = False
currUIdoc.Close
	
Set s = New NotesSession
Set db = s.CurrentDatabase
Set parentDoc = db.GetDocumentByUNID ( currDoc.ParentDocumentUNID )
	
Set newDoc = db.CreateDocument
newDoc.Form = "SomeForm"
	
newDoc.Field1 = parentDoc.Field1
newDoc.Field2 = parentDoc.Field2
.
.
.
Call newDoc.MakeResponse ( parentDoc )
Set newUIDoc = w.EditDocument ( True, newDoc )

FIELD history_mfg:=history_mfg;
FIELD created:=created;

date:= @Text(@Now);

name := "";

SUBJ := "<< Quote Request Notification From MFG - Project Ref# " + req_num + " >>";

BODY := SUBJ + @NewLine + "Request #: " + @Text(Incremented) +  "-" + req_num + @NewLine + "Piece Price: " + @Text(piecepc) + @NewLine + "Tooling Price: " + @Text(tooling) + @NewLine + "Comments Or Exceptions: " + body_notes + @NewLine + "See Link >> ";

@If(@IsNewDoc;@Prompt([Ok];"Notification!";"You Must Save The File Before You Can Initiate The Request.");@Do
(@If(@Prompt([YesNo]; "Send Memo?"; "A memo will be sent to Sales to notify them of your Quotation Response."); @Do(
@Set("name";@ProperCase(@Name([CN];@PickList( [Name] : [Single] ))));
@MailSend(name;"";"";SUBJ;"";BODY;[IncludeDoclink]);
@Prompt([Ok]; "Notification!"; "Your message has been summited.");
@SetField("history_mfg";history_mfg + @NewLine + "Your Sales Notification Was Sent To " + name + " On:      " + date);
@SetDocField ( $Ref; "SalesPublishDate"; @Now );
@Command ( [ViewRefreshFields] );
@Command ( [FileSave] );
@Command ( [CloseWindow] )
);
@Failure(@Prompt([Ok]; "Operation"; "Canceled")))))

• click on a button (or action) that opens a new form
• enter in values for an arbitrary number of new documents to be created
• click on a button (or action) to close the form and create all of the new documents
Simple, no? And quite elegant, I might add.]]>Tue, 7 Sep 2004 00:00:00 -04000http://ww2.nutechs.com/hosting/msobczak/Blogs/BlogSphere-1_0_2/LordLotusBlog.nsf/CommentsRSS?Open&id=8BEF0CC95073F8BB85256F090070E9E6http://ww2.nutechs.com/hosting/msobczak/Blogs/BlogSphere-1_0_2/LordLotusBlog.nsf/PostComment?RunAgent&id=8BEF0CC95073F8BB85256F090070E9E6http://ww2.nutechs.com/hosting/msobczak/Blogs/BlogSphere-1_0_2/LordLotusBlog.nsf/d6plinks/MSOK-63QJ56Notes DevelopmentMichael Sobczakhttp://ww2.nutechs.com/hosting/msobczak/Blogs/BlogSphere-1_0_2/LordLotusBlog.nsf/d6plinks/MSOK-63QJ56http://ww2.nutechs.com/hosting/msobczak/Blogs/BlogSphere-1_0_2/LordLotusBlog.nsf/d6plinks/MSOK-63QJ56
One of my customers reported a problem where an approver could not move a document to the next stage of the workflow. When the approver clicked on the [Approve] button, the rest of the code behind that button worked without generating an error, but the approval itself was not recorded in the document. I reviewed the code behind the [Approve] button, and noticed that the SaveOptions field was being set to "0" after the document had been saved in the UI (NotesUIDocument.Save). This was because after the document is saved in the UI, the document is then modified and saved via the back-end classes (NotesDocument.Save) by another routine. Setting SaveOptions to "0" will prevent the user from being prompted to save a document after it has been saved using the back-end classes. (Using SaveOptions to prevent the save prompt from appearing is a bad Lotusscript coding practice, in my opinion.)

For some reason, documents that still needed to be moved through the remaining workflow stages had the SaveOptions field set to "0". I suspect that there is a flaw in Lotusscript code executed somewhere else in the application that is allowing this to happen, but wouldn't be able to tell without digging deeper into the code.

What I did was change the code behind one of the workflow buttons so that it sets the SaveOptions back to "1" before saving it. That way, the approval will be recorded and saved, and that will move the document further along in the workflow. So, my advice to all out there: take care when using SaveOptions in your Lotusscript code. If you use it incorrectly, it will be very difficult to troubleshoot problems afterwards.]]>Thu, 29 Jul 2004 00:00:00 -04001http://ww2.nutechs.com/hosting/msobczak/Blogs/BlogSphere-1_0_2/LordLotusBlog.nsf/CommentsRSS?Open&id=79D38920B02B806585256EEC004B7563http://ww2.nutechs.com/hosting/msobczak/Blogs/BlogSphere-1_0_2/LordLotusBlog.nsf/PostComment?RunAgent&id=79D38920B02B806585256EEC004B7563