I wrote this for myself, but if you are interested, you can have a copy too. It is basically the Command and Function references from KiXtart 2001 user manual and OLE functions from KiXtart 95 user manual in one document. I have also included the @Macro list from the KiXtart 2001 user manual.

I have changed the format of the manual and tried to structure every command and function the same way for clarity. This included categorising some options on some functions and commands. I have used the words Required and Optional to show whether the option is needed.

Here is an excerp showing the formatting. I am using 2 fonts in the doc, but only one on this web page.

code:

---

CHR
Type		Function

Action		Returns the character representation of the ASCII code specified.

Syntax		CHR(number)

Parameters	number
		Required numeric that is the ASCII code of the character to convert.  Range is 0<number<255.

Returns		Character representation of the ASCII code.

Examples	$Message  = "Hello " + @USERID + chr(13) + chr(10) + "Welcome!"

		"The character is: " chr($ascii) ?

		IF chr($code)="A"
			"it's an A!!" ?
		ENDIF

---

I use words like numeric, string, keyword and variable declaration to show what is acceptable input.

This document is available on my (out of date) website or you can download it from here in Word 2000 format or rich text format.

Please read the disclaimer in the introduction of the document.

If you have any suggestions, please email me at chrismat@ozemail.com.au .

cj

P.S. Sorry if the formatting on the web page is broken.

[This message has been edited by cj (edited 12 April 2001).]

Have you looked at the KiXtart 2001 HTML help that ScriptLogic Corp. published?

It's nice. Not only is it a complete reference, but it also hyperlinks related commands to one another with "See Also".

The format is consistent and clean. It now even has a "Keyword Index" that includes a single hyperlinked page of all commands, functions and macros.

Worth checking out. http://www.scriptlogic.com/kixtart

[This message has been edited by bstyles (edited 12 April 2001).]

I only use my manual as a quick reference to remind me about the format of a particular function and keep it printed on paper (call me old fashioned) because I am not always at the computer when I am scripting or script-conceiving, so consequently don't require all that cool linking stuff.

I will be keeping SL's manual, keep up the good work!

cj