Configure Application --------------------- Restrictions: Sysops only (level 255) Allows you to specify the minimum privilege level required to use various database functions (list/search, add/delete, reply to an ad, and access co-sysop commands). Setting a minimum privilege level for co-sysops allows access to the following commands: Auto-Post New Ads Review/Edit New Ads Browse/Edit Database Delete Expired Ads Update Type 20 Database Export New to Text Statistical Summary Help with Sysop Commands The 3 R's ("Renumber Ads", "Rebuild All Indices", and "Remove Deleted Records") all require exclusive use of the database and are restricted to level 255 sysops only. The Configuration menu also allows you to specify the Maximum Number of Days that a user may leave an ad on the system. The valid range for this option is 1-999 days. If you specify "Y" to the "Automatically Delete Expired Ads" option, then each time the Type 20 Database is updated, ads which are expired will be automatically marked for deletion and skipped over. Note that there are several alternative ways that expired ads can be marked for deletion: - users may delete their own ads at anytime with the Delete command. - sysops can quickly find and delete expired ads "in bulk" using the Delete Expired Ads command. - finally, using the Browse/Edit command, sysops can manually delete expired ads on an individual case by case basis. Reply to a Classified Ad - This is an optional feature that can be completely enabled or disabled in the Configuration menu. In addition, you may also specify a minimum privilege level for writing replies. Replies are sent to the message base specified in the Config menu. When this option is enabled, users will be asked whether they want to accept replies for each classified ad that they enter. Also, when enabled, the Delete/Edit Ad command will allow users to toggle the "Reply" status of each ad they have previously entered. Many sysops have a "Sysop" menu implemented on their system, and most have a preferred exit key that is used on all menus. The next two configuration options allow you to customize ClassAds to conform to the standards already established on your BBS: Menu Character to access Sysop Menu : M Menu Character to Exit from a Menu : Q Any key may be entered that will not conflict with a key already in use in the ClassAds program. A validation sequence is used to ensure that you do not enter a "duplicate" or "reserved" key. Note: the "-" key has already been hard coded into the program as an alternative exit key. It may also be "entered" as an exit key if you want the "-" character to appear on the menus. Color - The format is: "code/code,code/code". The first pair of codes (separated by a "/") indicate standard foreground/background colors. The second pair of codes (following the comma) are optional and indicate edit field foreground/background colors. The ClassAd defaults are W/N,I which indicate white text on a black background, with INVERSE edit fields. The following color/attribute codes are supported: Code Color ---- ----- N Black B Blue G Green BG Cyan R Red RB Magenta GR Brown GR+ Yellow W White I Inverse * Blinking + High Intensity Using the same code for both foreground and background colors will cause text to display invisibly. The code for Bright White is "W+". If you wish to restore the default "colors" at any time, just delete the ADS.CFG file. This will force ClassAds to build a new one using the default settings. The final option is a Text File Header which, if specified, will be included at both the beginning and end of any text file generated with the Export command. You may want to try it with the included example before replacing it with your own version. See Help for the "Export" command for additional information. About Exclusive Use ------------------- When one of the exclusive use commands is selected, you will be notified if the database is currently in use, and you will be prompted to try again later. The following message is displayed: "Sorry, the database is in use. Please try again later..." This makes selecting exclusive use commands completely safe at any time. In addition, if a user attempts to access the database during the course of an exclusive use operation, they will be notified with the following message: "Sorry, the database is temporarily busy. Your request is" "scheduled and will be completed as soon as possible." "Your patience is appreciated... one moment please." This might occur, for example, if a user has been entering a new ad while you reindex the database. As soon as the reindex operation is completed, their new ad will be saved. Since all exclusive use operations are fairly brief and are self terminating, this rarely results in any interruption to users. In short, exclusive use operations have been designed to be safe to use while users are in the database. No harm should befall the data and the worst that might happen is that a user may be momentarily inconvenienced with a brief delay while an exclusive use operation is in effect. There are no actions that a sysop can perform that will hold the database open indefinately in exclusive use mode. However, for the convenience of your users, you may want to avoid using exclusive use commands when you know your system is relatively, busy or at times when you know there are several users in the program.