• Anonymous
  • Login
  • Register



Save any Note as Mime

Owners Timothy Parsons, Niklas Heidloff Category
Admin Utilities
Contributors - Platform
R 7.0.x
R 8.0.x
R 8.5.1+
R 8.5.x
Downloads 476Download latest release Last Release Feb 15, 2010
Rating
(0 ratings)
 Project Creation Feb 15, 2010
Status Not active Short URL Not defined
Description Save any Note as Mime In Catalog
No


===========
DESCRIPTION
===========
This is an example of a custom database driver which exports any note(s) as a MIME file.

To use this code, simply place ndbmime.dll into the Notes/Domino program directory. If the code will be running client-side, the DLL must be on each user's machine who will be executing the code, otherwise they'll receive an error message. If the code will be running on the server-side, the DLL must be placed in the Domino program directory. Additionally, the ndbmime.sym file should be placed in the program directory as well. This file is used by NSD in the event of a Notes crash, to help identify exactly where the code faulted.

==========
HOW TO USE
==========
To convert a note to MIME, simply call the code like this:
@DbCommand("mime" : "NoCache" ; "ConvertToMime" ; "<Server>" : "<FilePath>" ; "<NOTEID 1>" : "<NOTEID 2>" ; "<File path 1>" : "<File path 2>" )

Here's a break down of the options:

* "mime" Specifies which database driver to use
* "NoCache" Doesn't use caching for the call
* "ConvertToMime" The action to perform. This is the only action the database driver currently supports.
* "<Server>" The Domino server's name, or "" if running on a local database. i.e. Server/Cert
* "<FilePath>" The path to the database, i.e. s_dir\SupplyDb.nsf
* "<NOTEID 1>" This is a list of either note IDs or UNIDs. Each note ID or UNID specified in the list will be converted to MIME and written to disk. The note doesn't actually get updated in the database.
* "<File path 1>" This is a list of file paths to write the MIME to. i.e. c:\\temp\\note.eml
NOTE 1: any backslash characters need to be escaped with a backslash as shown here.
NOTE 2: Each file should use the .eml file extension. This is the typical file format for MIME messages.
NOTE 3: This should be a list of file paths. Each file path in the list correlates to the NOTE ID or UNID in the prior list. i.e. the first NOTE ID in the list will use <File path 1> as the path to write the MIME to.

=====
NOTES
=====
* A notes.ini setting can be enabled, dbmime_enable_logging=1. This enables logging for the database driver. Log statements will be written to a file named dbmime.log in the data directory.

* The files in the src directory are the source for this database driver. It was built using Visual Studio 2005. It also requires the Notes C API version 7.0.2 or higher to compile.

* The 'save as mime.lss' file contains some LotusScript which can be placed in an action button in a view. The code will convert the selected notes to MIME.


Timothy Parsons is the developer. Niklas Heidloff only committer.


Projects can have short and readable URLs, e.g. http://mobilecontrols.openntf.org.

You can request a short URL to your project by sending a mail to support at openntf dot org. Put the word 'OpenNTF' somewhere in the subject.
Owners are the people with maximal rights. For example they can create releases and add more contributors.

In order to define multiple owners use "," (comma) as separator.

Because of data privacy you cannot lookup other people's names but you have to type them in.
Enter the contributors or owners here who you want to receive notifications and questions by email.

In order to define multiple owners use "," (comma) as separator.

Because of data privacy you cannot lookup other people's names but you have to type them in.
In addition to the owners additional OpenNTF contributors have to be listed here. Contributors don't have the same access rights as owners, e.g. they cannot create releases.

In order to define multiple owners use "," (comma) as separator.

Because of data privacy you cannot lookup other people's names but you have to type them in.
Enter a short description of the project here (up to 100 characters).

The short description shows up in the project UI and in some of the views.
In this field you should enter a more detailed description of your project.

You can use the rich text editor for rich text formating. You can also enter HTML to embed objects, e.g. to embed a YouTube video or a screenshot of the project. In this case use '[' and ']' to mark the passthrough HTML as such.

Please note that the first time you use the new UI your description is converted from rich text to MIME. You might want to copy and paste the raw plain text from the old UI in the new UI so that you don't loose information.
A Catalog Release is for projects that are production ready and that are end-user "install friendly".

This property describes whether any release of this project has been added to the catalog.

Learn more about the catalog.