Subject: Approach Users Mailing List FAQ
Date: 31 Mar 1996 20:17:05 GMT
Summary: Answers to Frequently Asked Questions
 provided on the Approach Users Mailing List and the
 comp.databases newsgroup about the Lotus Approach database,
 as well as other material that may be helpful to a wide
 range of Approach users.

Posting-Frequency: monthly
  

              APPROACH USERS MAILING LIST FAQ
              ===============================

                     25 February, 1996


------------------------------

Subject: 1. Welcome

This FAQ contains a summary of answers to Frequently Asked
Questions (FAQ's) provided on the Approach Users Mailing List, as well as other material that may be helpful to a wide range of Approach users. 

At this stage the content relates to Approach v2.01 and 3.0*
unless specified as Approach 96.

Not all of the mailing list discussion makes it into the FAQ
because some of it will probably be of use only to the person who asked the question, and would therefore simply be wasting space in a FAQ. However that information is not lost. I maintain a database of all the posts to the mailing list, so if others ask similar questions at a later date I will answer with the information I have on record, and add it to the FAQ - if the question does in fact become 'frequently asked'.
  
  
------------------------------

Subject: 2. Table of Contents
  
        
Contents
========

     1. Welcome
     2. Table of Contents
     3. Notices
         \ UPDATE: How to get the latest edition of the FAQ
         \ Contributions, comments, corrections, or feedback
     4. Our collective wisdom so far...
         \ UPDATE: The latest version
         \ UPDATE: How does Approach compare to other DB's?
         \ UPDATE: Lotus Web Site and technotes
         \ UPDATE: Books
         \ Other information sources about Approach
         \ Stand-alone databases using Approach?
         \ Can Approach handle big databases?
         \ NEW: Getting started with joined databases!
         \ NEW: Working with Paradox database files
         \ OLD: Free Approach 3.02 Upgrade
         \ NEW: Calculating ages from birth dates
         \ NEW: Saving records in their sort order
         \ NEW: Header / Footer problems in v2.1
         \ Automatically opening files
         \ Automatically opening a particular form
         \ Automatic macro on opening/closing View file
         \ Deleting the body in summary reports
         \ Preserving found set when switching forms
         \ Keeping users out of design environment
         \ Searches on multipage forms
         \ 21st Century Dates
         \ MS-Windows 95 printing blank pages (v2 & v3)
         \ Radio Buttons Field Label
         \ Finding the previous weeks records
         \ Making empty fields disappear
         \ Running a Macro in a different .apr files
         \ Converting numbers to words 34 to thirty-four?
         \ Making keyboard entries into a formula or macro
         \ Sliding fields together on mailing labels
     5. How the mailing list works
         \ comp.databases
         \ Lotus
         \ Mail errors after posting to the list
         \ Mail storms
     6. Acknowledgments
         \ copyright notice and editor
   

------------------------------

Subject: 3. Notices
  
   
How to get the latest edition of the FAQ
----------------------------------------

Send an email to MAISER@rmgate.pop.indiana.edu with the words SEND AUML-FAQ.DOC in the body of the message.

This FAQ is approved by the *.answers moderators and is therefore also available at from the following sources:

Usenet: comp.databases, comp.answers, news.answers

<ftp://rtfm.mit.edu/pub/usenet/comp.databases/Approach_Users_Mailing_List_FAQ>

<http://src.doc.ic.ac.uk/usenet/usenet-by-hierarchy/comp/databases/Approach_Users_Mailing_List_FAQ>
  
Hypertext versions: (Note: These are converted from text to hypertext by the web sites NOT by me. Both of these services automatically convert URL references into links, but with varying degrees of success. The ohio-state document is also broken up into different pages for each contents item - very handy.)
  <http://www.cis.ohio-state.edu/hypertext/faq/usenet/databases/approach-mailing-list-faq/faq.html>

<http://ww.cs.ruu.nl/wais/html/na-dir/databases/approach-mailing-list-faq.html>
   
Contributions, comments, corrections, or feedback
-------------------------------------------------

I would appreciate any contributions, comments, corrections, or feedback that you want to make about the mailing list, the newsletter, or the FAQ. Post these to the mailing list the same as any other post or, if you really have to, you can email them to me at jabrown@unix.infoserve.net.
  
  
------------------------------

Subject: 4. Our collective wisdom so far...

The latest version
------------------

Approach 96 for Windows 95 is the latest version of Approach. It was released in December 1995 and contains significant new features including LotusScript 3.0 - a programming language that provides a development environment for robust, cross- product applications. To find out more about it see the following Lotus Web Page:
     
<http://www.lotus.com/ssuite96/approach.htm>

How does Approach compare to other DB's?
----------------------------------------

Articles about how Approach ranks against other databases, as well as handy hints, and how to optimize your productivity with Approach and SmartSuite, are available by searching back issues of PC World:

<http://www.pcworld.com>

Lotus Web Site and technotes
-----------------------------

Heaps of information including FAQs and hundreds of 'technotes' on every Lotus product, including all versions of Approach.

<http://www.lotus.com>

For all the Lotus FAQ's including a number for approach: 

<http://www.lotus.com/csswww/faqwin.htm>

Technotes are Lotus's answer about a whole range of problems
people encounter using Lotus products and answers to frequently asked questions. They are also available via ftp. 

<ftp://192.216.79.100/pub/desktop/Approach/technotes/text/00_index>
      
Books
-----

The following books have been recommended in posts to the
Approach Users Mailing List:

   * The manuals that come with Approach (!)

   * Mastering Lotus Approach by Powell (Sybex/Lotus Books)
          (This is the most highly recommended book)

   * Approach 3.0 for Dummies

   * Practical Approach version 3.0 by Siegel (MIS Press)

   * Using Lotus Approach 3 by Plotkin (Que)

   * Introduction to Databases" by James T. Townsend
          (recommend for business uses who are learning and
           designing databases)

Other information sources about Approach
----------------------------------------

   * Lotus fax - back service (free) (+1) 800-346-3508
           (These are also available from the Lotus Web Page
            as Technotes)

   * Back issues of PC World. Search index located at: 

<http://www.pcworld.com>

   * The Approach BBS: (+1) 415-335-2362

   * Do It With Lotus SmartSuite (newsletter)


Stand-alone databases using Approach?
-------------------------------------

No, there is no way of creating fully stand alone' database
using Approach. There are currently no run time compilers for Approach that I am aware of, but it is rumored that one is under development. Approach is designed to be a 'Front End'. The idea is you can take an existing database (dBase, Access, Excel, Foxpro, Oracle, Paradox, SQL, 123 ...) and create your own Front End, leaving the original database intact for others. Or you can develop your own database from scratch. You can also develop a View files with Macros that give it the appearance of a full-blown 
application and distribute to other users, but everyone who uses it needs their own copy of Approach. Purchasing site licenses and using Lotus' concurrent licensing scheme will greatly reduce the costs for businesses.

Using the Customizing Approach chapter in the user's manual you can be completely customized so that your users can't trash the database that you build for them. Pay particular attention to the Setting Preferences, Defining Passwords for Files, Customizing SmartIcons, and Customizing Menus sections. Also review procedures for defining basic field settings in the various views you give the user. You can design your database using custom pull-down menus and various buttons on forms so that all the native con
trols in Approach can be turned off or hidden from the user.

Approach 96 will include LotusScript which will give you much the same capabilities of Access Basic. But all is not lost for v2.* and v3.**! You may be able to write the routines you need in some other language, such as Visual Basic. These routines could be activated by a Windows macro (i.e. Recorder).
   
Can Approach handle big databases?
----------------------------------

Well, it probably depends on what you call big, the design of your database, and what hardware you have. A number of
subscribers have reported having in excess of 40,000 records
without any difficulties. As far as I am aware Approach does not have a 'maximum' number of records.

Having the latest version of Approach on a suitably fast system with plenty of RAM (8 meg or more), fast disk access, and fast disk caching will of course increase the performance of any large database, but you may also what to carefully consider your database design. A badly designed database will perform poorly in any application... For instance, the more joins you have, and the more joined database shown on one form, the slower your database will tend to be, and databases work slower with 'full record l
ocking' than with 'optimistic record locking'.

Getting started with joined databases!
--------------------------------------

Understanding relational (or "Joined") databases is a big area, but is vital to fully utilizing a program such as Approach. Start by do some reading. Some books are recommended earlier in the FAQ, but don't forget the Approach manual either. It briefly takes you though the process of setting up joined databases. Looking at the example databases that come with Approach will also help you understand how the different data in different databases is linked together to provide many facilities that are not possi
ble in flat databases.

Working with Paradox database files
-----------------------------------

A number of people have reported indexing and General Protection Fault problem when working with Paradox files in Approach v3.00 and v3.01 on MS-Windows v3.1x and v95, and v3.02 on MS-Windows 95. The most stable combination seems to be Approach v3.02 on MS-Windows 3.1. However, you will probably be better off converting your database files to dBase 1V.

Free Approach 3.02 Upgrade
--------------------------

According to the technotes available at the Lotus web site <http://www.lotus.com>, version 3.02 of Approach is available free to customers experiencing an issue with Approach 3.0. Technotes on the following topics all contain the phrase, 'This issue has been addressed in Approach 3.02':

     * Only One Mailing Label Prints Per Page
     * Error: Unable to Build Index Required for XXX
     * Fill Field Option is Grayed Out in Browse/Worksheet
     * Stack Overflow Running Approach 3.0 QuickStart Tutor.
     * Import Table Has Changed, Unable to Import Data
     * Sending the Current View Only Sends All Views
     * General Protection Fault in Module KRNL386.EXE
     * Record Header Size... Bytes Too Small Saving an .APR
     * Form or Report Places Fields on Top of Each Other
     * Repeating Panel Will Not Sort in Approach 3.0
     * Crosstab Repeats the Same Value in Each Row
     * Changing Number to Boolean Returns Incorrect Results
     * Slow Performance using PowerClick for Grand Total
     * Internal Error - Couldn't Load String 1035 with Spell
     * Approach Export Macro to Fixed Length Inserts Spaces
     * Find Using a Wild Card Returns Blank Date Fields
     * Error: No Records Found Finding Times in DB2 Database
     * Error: Out of Disk Space Finding a Date in SQL or DB2
     * Fields Formatted as Zip Code Corrupt Data in Approach
     * Error: Macro Step Not Valid Editing Valid Macro
     * Percent Format Displays Zeros after the Decimal

So, if you are having troubles in any of the above areas it may pay to check what version of Approach you have (by selecting Help: About Approach). If you are using 3.00 or 3.01 then you may be able to get a free upgrade to v3.02 by contacting Lotus.

Calculating ages from birth dates
----------------------------------

The following formula produces a line of text e.g. "Age: 32 yrs 6 mths". If the PEOPLE.BIRTHDATE is empty them it produces an empty text string i.e..''

If(Isblank(PEOPLE.BIRTHDATE), '', If((Month(Today()) - Month(PEOPLE.BIRTHDATE)) < 0, Combine('Age: ', (Year(Today()) - Year(PEOPLE.BIRTHDATE) - 1), ' yrs ', (12 + Month(Today()) - Month(PEOPLE.BIRTHDATE)), ' mths'), Combine('Age: ', (Year(Today()) - Year(PEOPLE.BIRTHDATE)), ' yrs ', (Month(Today()) - Month(PEOPLE.BIRTHDATE)), ' mths')))

Alternatively the formula Today() - PEOPLE.BIRTHDATE gives you the persons exact age in days. You can then roughly calculate how many years and months, but since months and years are different lengths the answer is an approximation, give or take a few days.

Saving records in their sort order
----------------------------------

Sort the records as you want them, and then export (ALT-FILE-EXPORT) that database into a new .dbf file. This .dbf must contain the same files as the old .dbf. Delete the old .dbf and rename the new .dbf with the old .dbf file name.  e.g. Say you have a database called PEOPLE.DBF. Sort the records and export all the fields in PEOPLE.DBF into another database called TEMP.DBF. Exit Approach. Delete PEOPLE.DBF. Rename TEMP.DBF as PEOPLE.DBF.

Header / Footer problems in v2.1
----------------------------------

People have experience problems where the top or bottom half of the footer or header line is cut off in v2.1. The easiest way to get rid of this type of problem is to recreate the report from scratch - this is likely to be quicker and easier than spending to much time playing with your current one. 1) set the printer setup to the correct values  2) create a very simple report using all the default values. Just specify  a couple of fields from the database the report is based on.  3) immediately insert and 
set up the footer and header as required. Do a couple of test prints to make sure it is right.  4) finally, set up the report contents the way you want it - insert further fields, do formatting etc...

Automatically opening files
---------------------------

Make sure .apr (.vew for v2.1) extensions are associated with Approach. You can do this in the File/Associate menu of File Manger. Then create a Windows program item with a command line something like: 

c:\path\database.apr (for >v3.0*)

where a:, \path, and database.* are the drive, path, and
filename of your database file.

To automatically open several files use the command line:

c:\approach\approach.exe c:\path\db1.apr c:\path\db2.apr

Use .vew instead of .apr for v2.1 files

Automatically opening a particular form
---------------------------------------

Approach automatically opens the form that you had up on the
screen the last time you saved the .apr file (or .vew in v2.1). So next time you make some changes make sure the right form is on the screen when you save it. Alternatively you can set up a macro to automatically change to that form when the database is opened. (See "Automatic macro on opening/closing View file")

Automatic macro on opening/closing View file
----------------------------------------------

You can create a macro that runs automatically each time you
open a particular approach view file by assigning it the name "OPEN". Similarly, if you assign the name "CLOSE" to a macro it will run each time you close it's associated file.
   
Deleting the body in summary reports
------------------------------------

Use your mouse to drag the bottom line of the body frame up
above the top line of the body frame. That way the body
disappears and only the summary lines show up on the report.

Preserving found set when switching forms
-----------------------------------------

Make sure all of your forms are based on the one database. When creating a new database do not create the .vew or .apr based on that database (or delete it if you do). Instead, create your new form based on your main database rather than your newly created one.

Keeping users out of design environment
---------------------------------------

If you are using v3.0* you can set a design mode password by
selecting the Tools/Preferences/Password menu item. Approach
will then not let anyone in design unless they know the password (even by status bar, icon or key combination).

Read on if you are using v2.1, or if you would also like to
remove the temptation of changing the form:

Menus can be customized so that the design environment option never appears.  Apparently, custom menus are kept in .APR files so that no custom files on user PCs would be required.

Icon bars can be customized so the design environment icon never appears.

The status bar on the bottom of the Approach window will let the user go into the design environment. The status bar can be suppressed but this prevents the user from reading useful
information such as current record number and how many records were found out of how many.  There are no Approach macros and formulas that support display of such record information on a form. 

In v2.1 there is no way to prevent a user from getting into the design environment via CTRL-D. 

.APR / .VEW files can be made read-only by changing their
properties in File Manager, but if a user gets into the design environment, Approach won't tell them they cannot save design changes until they try to save their changes, and they may know how to change the file properties.

Searches on multipage forms
---------------------------

Make a single page form that contains all of the fields that you want to search on. Switch to this search form, do the find, and then switch back to your multipage form. The found set will be preserved as long as search form must also be based on the same database as your original multipage form.
   
21st Century Dates
------------------

If you enter the full year (e.g. 10/31/2001) you should not
encounter problems. However, if you want to enter dates like
10/31/01, and you want to add only future dates you can use the following solution.

Create 3 variable fields, all 2 digit numbers: VYear, VMonth, VDay. Display these three fields on your form. Enter the dates using these three fields. Create a calculated field called VEYear containing the formula If(VYear => 95, (If(VYear <= 99, VYear, VYear + 2000)), VYear + 2000.

Then create another calculated field called, say, DISPLAYDATE containing the formula: DATE(VMonth,VDay,VEYear). DISPLAYDATE will contain the full 21st century date.
     
MS-Windows 95 printing blank pages (v2 & v3)
-------------------------------------------

To stop Approach from printing out a blank page after every
printed page in Windows 95, make the following change to your WIN.INI file: Under the [Compatibility] heading change
'Approach=0x0004' by putting a ';' in front of it so that it
reads ';Approach=0x0004'. 
   
Radio Buttons Field Label
-------------------------

Question: When using radio buttons, why can't I maintain the
field label, as in getting it to appear above / below / etc. / anywhere in the box?

Page 6-12 of my User's Guide shows an example with a field label Type of Customer. But I have been unable to generate a similar example.

Answer: They got tricky. What they did to accomplish that is to create a Text Box and type the box label Type of Customer. Then they created their Radio Buttons box (outside of the text box, clicked the right mouse button, chose ARRANGE, BRING TO FRONT, and then dragged the radio buttons on top of the text box they way they wanted it.

Play with it a bit and you'll get the results you're looking for.
   
Find the previous weeks records
-------------------------------

For the previous week (Sun - Sat): ('date'= your date field)

     if(weekofyear(date)=weekofyear(today())-1 and
          year(date)=year(today()))

If the data is only for one year, then you can leave out the
'and' and all that follows.
   
For the last 7 days: (including today) 

     >=@TODAY()&<=@TODAY()+7
  
Or, if you need to find records produced during the last 7 days:

... starting with and including today's date, use the formula: 

     >=@TODAY()&<=@TODAY()+7
 
Make empty fields disappear
---------------------------
     (... rather than just turn invisible)

It is possible on reports but not on forms.

An alternative is to set up a multipage form and have a separate page for each field. On the first page, put a check box for each field set to automatically come on if there is an entry in the field. Then, when you are browsing through the forms, you look at the page if you need to.
  
Running a Macro in a different .apr files
-----------------------------------------

One way of doing this would be to use  the Windows Macros
(Recorder) rather than Approach Macros.
  
Converting numbers to words 34 to thirty-four?
----------------------------------------------

There isn't such a function in any version of Approach. What you need to do is create another database with the numbers and related text versions of the numbers and join it into your current database to the field that you want to appear as text.

It might look something like this:

     number     text
       1        one
       2        two
      ..        ...
      27        twenty seven

(If have database containing this data, could you please export it and email it to me at jabrown@unix.infoserve.net, so that I can make it available to everybody. JB)
   
Making keyboard entries into a formula or macro
------------------------------------------------

To do this, link every record in your database to a single
record in a specially created database. Fields in this record in the special database can be easily changed by putting the fields on any form, and can be used to input information required by any macro or formula. The method for doing this in Approach v2.1 is as follows:

  1) In your existing database (let's call it EBASE) create a new field called (say) DUMMYLINK, and set the field definition options so that a '1' is automatically entered into DUMMYLINK every time a new record is created. Then enter a '1' into the DUMMYLINK field in all existing records. The end result of this is that every record in EBASE will always have a '1' in the DUMMYLINK field. Once it is set up there is no need for DUMMYLINK to appear on any forms.

  2) Then create a new database (INPUTDBASE), with two fields INPUTDATA, and DUMMYLINK. Create one (and only one) record and enter '1' into the its DUMMYLINK field. Then join INPUTDBASE to EBASE by the DUMMYLINK fields. The data you enter into the INPUTDATA field is now linked to every record in EBASE. 

  3) Put the EBASE:INPUTDBASE field onto any form or forms you commonly use.

  4) Create the macro or formula using the EBASE:INPUTDBASE
field where you want to input data.

e.g. In an phone book database you could enter your current
location into the INPUTDATA field. This information could then be used by various formulas to calculate the actual phone numbers you need to dial from there, including any national, or international codes, as well as perhaps giving the time and date at the destination.

(Could somebody please confirm if this procedure is required for v3.0x)
   
Sliding fields together on mailing labels
-----------------------------------------

If you are having difficulty getting fields to slide together on mailing labels (such as first and seconds names), try setting up a formula that combines the fields in the format you want, and then print the formula instead of the individual fields. 

An easier way of dealing with this problem is to create a text object and embed the fields in it. The fields are expressed as <<database.field>> where DATABASE is the name of the database and field is the name of the field.
e.g. <<database.city>>, <<database.state>> <<database.zip>>
 
------------------------------
  
Subject: 5. How the mailing list works
  
   
It is fairly simple, but before we get into it please remember one thing: The best source of information about how to use Approach is the printed manual and the help files that come with it. If you have access to the World Wide Web you may also want to check out the technotes and FAQs on the Lotus WWW site:

<http://www.lotus.com>.

The Approach Users Mailing List is a discussion area for anyone uses or provides user support for the Lotus Approach relational database. Subscribers also receive an occasional newsletter summarizing recent additions to the FAQ as well as other relevant information and notices.

The Approach Users Mailing List is not moderated.  Any message sent to it is automatically bounced back out to everyone on the list.  While I in no way want to stifle free discussion, as list owner I reserve the right to step in if a flame war erupts that becomes tedious for other subscribers, or if someone becomes unseemly (excessive use of profanity, for instance).

You may choose to receive the mailing list as normal individual emails, or to receive all the posts for each day compiled into a single 'Digest'.

     <<<< == VERY IMPORTANT ==>>>>

Please read the remainder of this section very carefully, as
this mailing list has two different addresses for different
purposes, and errors will occur if you use the wrong one.

     <<<<== SAVE THIS MESSAGE NOW ==>>>>
                              ^^^

You should keep a copy of this section on your computer so that you can refer to it in the future. This is particularly handy if you want to know how to subscribe or unsubscribe one day in the future.

If you have a personal message for someone, please send it to their address, not the list server address.  Any mail sent to the APPROACH List Server address will automatically be sent to everyone on the list.

The list has two addresses. One is the APPROACH List Server
address, and the other is the MAISER Command address:

The MAISER Command address is: MAISER@rmgate.pop.indiana.edu
    ==============

It recognizes the following commands in the body of the message (NOT THE SUBJECT LINE):

     SUB APPROACH         to subscribe
     UNSUB APPROACH       to unsubscribe
     SET APPROACH DIGEST  to turn on the digest option
     SET APPROACH MAIL    to turn off the digest option
     HELP                 to receive the MAISER help file
     INDEX                to receive a list of files
     SEND AUML-FAQ.DOC    to receive the Approach Users
                               Mailing List FAQ
     SEND LIST.TXT        to receive a list of other mailing
lists at this site. To subscribe to them send a message to the MAISER Command address with SUB listname, e.g. SUB INROOTS in the body of the text.

LISTSERV commands do not work. MAISER will only recognizes the commands shown above.

ALL COMMANDS SHOULD BE SENT TO THE MAISER COMMAND ADDRESS. ENTER THE COMMAND AS SHOWN BEGINNING WITH THE FIRST LINE OF YOUR MESSAGE. MULTIPLE COMMANDS CAN BE SENT AT ONCE, ONE PER LINE WITH NO BLANK LINES BETWEEN THEM.

The APPROACH List Server address is:
    ====================
                             APPROACH@rmgate.pop.indiana.edu
 
Do not send commands to this address! All posts sent to the
APPROACH List Server address will be immediately sent out to
everybody on the list. Make sure you are using the correct
address, and that you have not made any errors or omissions in your message.

If you have any difficulties with the mailing list please email me at jabrown@unix.infoserve.net with APPROACH in the subject line.

Question and Answer Posts 
-------------------------

I suggest you use the following format:

     a) Summarize your question in one sentence, being as
specific as you can. E.g. 'Is it possible to save records in
alphabetical order?'

     b) In a short paragraph following the question, provide any further information that people may need in order to fully understand your question E.g. 'I find it annoying to have to continually sort the records and it would be easier if I could just save them in their sorted order. Is this possible?'

     c) In a final paragraph state what version of Approach you are using (2.1, 3.0,...) as well as any other software or hardware that you refer to. THIS IS VERY IMPORTANT.
      
comp.databases
--------------

There is no official association between the mailing list and the Usenet newsgroup comp.databases, or any other newsgroup. However comp.databases is a good forum for discussion. Relevant information gathered from the newsgroup will be included in the Newsletter and FAQ. If you do post to comp.databases please include the word 'APPROACH:' in the subject line, preferably a the beginning in capital letters, so that it shows up clearly in a subject line search. e.g. Subject: APPROACH: Can you save sorted recor
ds? Remember, most people on the mailing do not regularly access comp.databases.
    
Lotus
-----

There is official no connection between this mailing list and the Lotus Corporation what so ever. This is a completely
unofficial and unconnected mailing list.

Mail errors after posting to the list
-------------------------------------

You may sometime receive an error message from various mail
servers after you have posted something to the mailing list. If it contains words like 'undeliverable' or 'unrecoverable' you should forward them to me at jabrown@unix.infoserve.net. Mail servers should do this automatically but many do not. Error messages containing words like 'warming, message could not be delivered for 4 hours' can generally be ignored, but make sure you have read it properly first. Error messages from .rmgate.indiana.edu are usually directed at you personally, and generally means that 
you have done something wrong. Email me if you cannot work out what it is.
  
Mail storms
-----------

A mail storm is caused by a mail server which incorrectly sends error messages to the mailing list instead of the Error_to: address in the message header. When it sends an error message to the list it sometimes causes the same error to be repeated. This goes on and on and our inboxes quickly fill up with recurring error messages. This is what is called mail storm. They are unusual, but one has occurred in the life of this mailing list.

There is nothing I can do to stop this from happening because it is caused by an error in the remote system. I am able to remove the offending address from the mailing list when I log on and discover the problem, but the mail storm will probably have been stopped by the mail server before I do this.

I will however make a complaint to the postmaster of the
offending system, asking them to permanently correct the problem.

If this ever occurs again DO NOT SEND ANY MAIL TO THE LIST AS IT WILL ONLY MAKE THE SITUATION WORSE BECAUSE EVERY ADDITIONAL MESSAGE SIMPLY INCREASES THE RATE OF THE MAIL STORM.

I will appreciate your understanding and cooperation with this, as will everybody else on the list.
   
  
------------------------------
  
Subject: 6. Acknowledgments
  
   
The following people have contributed information to the mailing list which is contained within this FAQ:

     Mike Armour
     Anthony Barker
     Bill Bosking
     'CedarsMT'
     Sue Clark
     'emdurkin'
     Richard A. Garrard
     Charles T. Hall
     'Bobj19'
     'JoeF3900'
     Peter M Ladstaetter
     Lewis N. Payton
     Donald Ravey (comp.databases)
     R M Reddicks
     Bernie Sakel (comp.databases)
     Ben Schorr
     Scott 'pccscott'
     David Sherman
     Bill Tarkulich
     Patrick Timmins
     Walter Thompson
     Doug Tymes
     Doug S. Varney
     Bernard Victor
     Mark Wright

Some information was also gathered from the Lotus Web Site.

If you would like you name added to this esteemed list, please feel free to post some helpful suggestions and answers to the Approach Users Mailing List.

This document is provided as is without any express or implied warranties. The editor and contributors assume no responsibility for errors or omissions, or for damages resulting from the use of the information contained herein.
    
(C) Copyright 1996 by John Brown, all rights reserved.
Permission is given for this document to be distributed in
electronic form (such as email, newsgroups, and the WWW) as long as it is posted in its entirety including this copyright statement, and is not distributed for financial gain.

Editor: jabrown@unix.infoserve.net (John Brown)
   
