Readme file for AprScript Utility
Author: Keith Seeley
Date: 4/2003


The AprScript utility is used to create an export of all scripts in an .apr file.
THe default format is a text file which is created in the same directory as the apr, suffixed with "_Scripts.txt"
If all scripts are small enough to fit into dbt memo fields the utility will prompt you to create a dbf.




1) Files supplied:

AprScript.lso		'Lotusscript object file.
AprScript.lss		'Lotusscript script file.
AprScript.dbf		'Empty Template .dbf
AprScript.dbt		'Empty Template .dbt
AprScript.adx		'Empty Template .adx
AprScript_Readme.txt	'This file

Copy all files into C:\lotus\approach\ directory.
If the directory does not exist, create it.





2) Usage:

- Close all open apr's.
- Open the apr from which you want to extract the scripts.
- Open the script editor.
- Add the following under Globals, Options:
	Use "c:\lotus\approach\AprScript.lso"

- Create a sub and add the following
	sExportScripts

- Run the newly created script FROM THE SCRIPT EDITOR.

* The script editor MUST be open for this utility to function properly.




3) Known Issues:

- Approach 9.1 and earlier have a string length limit of about 32,000 characters.  An apr containing a script larger than this will generate an error in these versions and that script will not be logged.

- DBF creation only: This utility will export up to 64,000 characters into a memo field (the viewable size limit for Approach).  However, due to a bug in Approach versions prior to A9.8,  you can view but not enter/edit/copy memo fields containing more that about 32,000 characters.




4) Platforms supported:

- Approach versions A97 and above.
- Windows 98 and above.
- Windows NT 4.0 and above.





5) General comments:

The utility is provided "AS IS".  The author is not liable for use/mis-use of the product.

All code is freely distributable, but I ask that a simple acknowledgement be made to this author.

The script file AprScript.lss supplied with the download gives you the ability to modify the code.
If there's anything you don't like about the utility, change it! (please RENAME the lss/lso if you do)

Please direct questions about this utility to XpertSS.com, Approach-Chat section (unless directed otherwise by XpertSS staff!).  Emails sent directly to me will be ignored.




6) Notes about LSO and LSS files in Approach:

Both LSO and LSS files contain un-compiled script code.  The LSS file is easily viewed using a text editor while the LSO is a proprietary Lotus format which cannot be accessed.

The LotusScript Object file, LSO, is compiled at run time as a SEPERATE module.  This means that all private declarations in the LSO are only visible within the scope of the LSO.

The LotusScript Script file, LSS, is compiled at run time INTO THE CURRENT Globals module.  This means that declarations in the LSS MAY conflict with declaration in your scripts.

If you are recieving errors when trying to %INCLUDE the LSS you will have to Rem out any duplicate declarations from your script.  In addition, the code in the AprScript utility REQUIRES Option Compare Nocase, so make sure that if you use the %INCLUDE that your code will function properly with that option.

There should be no compatibility issues when using the LSO.




