Search DominoPower's 11,960 Lotus-related article archive 
Home
EasyPrint
News details Click here for the RSS feed's XML code. This is not a browser URL.
Articles-only Click here for the RSS feed's XML code. This is not a browser URL.
Twitter Feed Click here for the Twitter feed.
CREATING CUSTOM APPLICATIONS
Distributing applications to remote users
By Richard Echeandia

In last month's article, "Cascading custom applications on your Domino server," we reviewed how to make your custom Notes applications behave like cascading address books on your Domino servers. This month we'll complete the project by creating a way to perform the same function on your Notes workstations.

Working with remote or "occasionally connected" users requires you to write your applications and perform your administration differently than in a LAN-locked environment. Remote users are generally more support-intensive and configuration dependent than your always connected server users and one of the more vexing problems that administrators can have is in deploying Notes applications into the field.

It's a fairly common practice to send buttons that perform various administrative functions to your users via a Notes email message. The one button that I've seen mailed most frequently adds Notes databases to a user's workspace and creates any required environment variables. These buttons are, of course, real times savers, and most of us have one or more of these in our toolkit. For this month, we're going to combine those functions with local replication and then perform the steps necessary to cascade the database in the local user's NOTES.INI file.

Back to the example
For the purposes of our example, let's go back to last month's example and assume that the database we want to deploy locally to our users is located on the Dallas/Fort Worth server "DFW001" and is called "APPS\ROLODX.NSF". Using the configuration items described in last month's article you (or your developers) should have created a database that contains the views and fields required to work as an address book. The coders, testers, and beta users of the application all feel like proud, happy parents and management is ready to see this thing in production.

How do you get this creation out into the field? Create a button with the logic shown in the attached listing, change the name of the server and the database where indicated in the source code, then mail it off to all the users of the application.

Walking through the code
Let's look through the code, available at http://www.component-net.com/dp-extras/ini1198.html, and see what we've got to do.

The code in the listing should be placed in the Click event of a normal LotusScript button. The first things that you should put at the top of the script are the application specific variables. That way, when you use this button again (you do want to re-use code as much as possible right?), all that you'll have to do is change the header section and the rest of the logic can remain unchanged. Lines 3 through 5 perform the setting of these variables. Next, lines 8 Ð 12 perform the normal LotusScript setup processing for our script.


1  ·  2  ·  Next »
Other articles you might like
Home > Lotus Technologies > Domino (77 articles)
   More about Domino log files
   Why your log.nsf might not be purging properly
   Sloppy analysis at the core of another Domino vs. SharePoint report
Home > Tips & Techniques (102 articles)
   More about Domino log files
   Why your log.nsf might not be purging properly
   A faster way to repair corrupted server files
Get Weekly Email Updates
Subscribe to our regular weekly email newsletter. It's packed with tips, reviews, deep analysis, and the latest news.
 
Recent DominoPower Articles
It's time for Lotus to double-down on Linux and open source
Back to basics with Notes: what you can do now
Back to basics with Notes: what are the basics?
Back to basics with Notes
Smart Upgrade bug in Domino 8.5.1 (and some work-around tips)
Hands-on with XPages and the Lotus Solutions Catalog
A tool for migrating Exchange to Domino
Latest Lotus Headlines
Domino 8.5.1 mail routing problem solved
A small tip for upgrading your XPages apps from 8.5.1 to 8.5.2
What is in your plugin_customization.ini?
Email Classification - What and Why?
Database transfer in IBM Lotus Quickr 8.5 for WebSphere Portal
If you are an Admin please read this - Rule No 1 The Comms Rule
Tell me about how you use the Day-at-a-Glance sidebar (or not)
>> Read all the news
More from the ZATZ journals
Computing Unplugged: Smartphone smarts for a mobile world
David Gewirtz Online: CNN commentary and analysis
OutlookPower: The strange case of Outlook losing notes and requiring passwords
-- Advertisement --

Navigate the Document 'SharOllaboraGement' Universe
More than 60% of organizations are dealing with 'Content Chaos' -- Out of control Documents and Content.

Unfortunately, over 50% of those will rush into the wrong solution and ultimately fail.

The Document & Content Management Decision Matrix is a free tool for navigating the broad 'Document Sharing, Collaboration and Management' technology universe.

Use it to help you make the right decision based on your organizational preferences and needs.

Tap to download this complementary tool.

-- Advertisement --

Want the top Lotus experts by your side without paying hefty consulting fees?
Look no further.

Like having a team of consultants by your side -- ones who have all the answers and never make mistakes -- THE VIEW gives you immediate access to field-tested instruction, guidance, and best practices from the brightest Lotus professionals around.

See the new instruction, advice, and best practices added to THE VIEW this week.

ZATZ Home  ·  News  ·  Back Issues  ·  Credits/Trademarks ·  Link To Us
Copyright © 1998-2010, ZATZ Publishing. All rights reserved worldwide.
Editor's Login