[ver]
	4
[sty]
	
[files]
[charset]
	82
	ANSI (Windows, IBM CP 1252)
[revisions]
	0
[master]
	C:\AMIPRO\DOCS\V4\adg1toc.SAM
	
	0
	0
	0
[sequence]
	4
	0
	0
	0
	23
	0
	Numbered list
	0
	Bullet
	0
	Indnt bullet
	0
	Indnt caution
	0
	Indnt tip
	0
	Indnt note
	0
	Caution
	0
	Tip
	0
	Note
	0
	Browse
	0
	Keyword
	0
	Context
	0
	Title
	0
	Macros
	0
	Alink
	0
	Butnbar
	0
	Window
	0
	Win95 macros
	0
	Win31 macros
	0
	Build tag
	0
	_COND_IF
	0
	_COND_ELSE
	0
	_COND_ENDIF
[prn]
	PostScript (QMS)
[port]
	LPT2:
[lang]
	1
[desc]
	What Is a Notes Application?
	
	
	
	
	801447154
	142
	769804754
	2351
	18
	0
	0
	0
	0
	
	
	
	
	
	
	1
[fopts]
	0
	1
	0
	0
[lnopts]
	2
	Body Text
	1
[docopts]
	5
	2
[GramStyle]
	
[ParaNum]
	1
[tag]
	Body Text
	2
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		0
		0
	[spc]
		24
		200
		4
		19
		60
		3
		100
	[brk]
		100
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		
		0
		1
		1
		0
		0
		0
		0
	[nfmt]
		280
		1
		2
		.
		,
		$
	Body Text
	5
	1
	480
	1
	960
	1
	1440
	1
	1920
	1
	2400
	0
[tag]
	Crossref
	3
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		513
		3
		0
		300
		600
	[spc]
		24
		200
		4
		19
		0
		3
		100
	[brk]
		4
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		
		0
		1
		1
		0
		0
		0
		0
	[nfmt]
		272
		1
		2
		.
		,
		$
	Crossref
	0
	0
[tag]
	Bhead title
	4
	[fnt]
		Arial
		200
		0
		16385
	[algn]
		1
		1
		0
		0
		0
	[spc]
		40
		220
		4
		79
		0
		3
		100
	[brk]
		80
	[line]
		16
		0
		3
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		2
		
		0
		1
		1
		0
		2
		0
		0
	[nfmt]
		272
		1
		2
		.
		,
		wr
	Body Text
	0
	0
[tag]
	Chead title
	5
	[fnt]
		Arial
		180
		0
		16385
	[algn]
		1
		3
		0
		0
		0
	[spc]
		40
		200
		4
		79
		0
		3
		100
	[brk]
		112
	[line]
		16
		0
		3
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		3
		
		0
		1
		1
		0
		2
		0
		0
	[nfmt]
		272
		1
		2
		.
		,
		wr
	Body Text
	0
	0
[tag]
	Dhead
	6
	[fnt]
		Arial
		180
		0
		16385
	[algn]
		1
		3
		0
		0
		0
	[spc]
		40
		200
		4
		100
		0
		3
		100
	[brk]
		68
	[line]
		16
		0
		3
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		4
		
		0
		1
		1
		0
		2
		0
		0
	[nfmt]
		272
		1
		2
		.
		,
		$
	Body Text
	0
	0
[tag]
	Ahead
	7
	[fnt]
		Arial
		220
		0
		16385
	[algn]
		1
		3
		0
		0
		0
	[spc]
		40
		240
		4
		79
		0
		3
		100
	[brk]
		112
	[line]
		16
		2160
		3
		0
		1
		1
		1
		65
		10
		1
	[spec]
		0
		1
		
		0
		1
		1
		0
		2
		0
		0
	[nfmt]
		272
		1
		2
		.
		,
		wr
	Body Text
	0
	0
[tag]
	Numbered list
	8
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		300
		300
	[spc]
		40
		200
		4
		19
		60
		3
		100
	[brk]
		36
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		5
		<*:>.
		0
		3
		1
		0
		2
		0
		0
	[nfmt]
		272
		1
		2
		.
		,
		$
	Numbered list
	0
	0
[tag]
	1st lev para
	9
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		300
		0
		0
	[spc]
		40
		200
		4
		19
		60
		3
		100
	[brk]
		68
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		
		0
		1
		1
		0
		0
		0
		0
	[nfmt]
		272
		1
		2
		.
		,
		$
	1st lev para
	0
	0
[tag]
	Bullet
	11
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		120
		180
		180
	[spc]
		40
		200
		4
		19
		60
		3
		100
	[brk]
		36
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		</U>
		0
		3
		1
		0
		0
		0
		0
	[nfmt]
		272
		1
		2
		.
		,
		$
	Bullet
	2
	1
	160
	1
	400
	0
[tag]
	Indnt bullet
	12
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		420
		180
		180
	[spc]
		40
		200
		4
		19
		60
		3
		100
	[brk]
		36
	[line]
		16
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		</U>
		0
		3
		1
		0
		0
		0
		0
	[nfmt]
		272
		1
		2
		.
		,
		$
	Indnt bullet
	0
	0
[tag]
	Bhead
	0
	[fnt]
		Arial
		200
		0
		16385
	[algn]
		1
		1
		0
		0
		0
	[spc]
		40
		220
		4
		180
		0
		3
		100
	[brk]
		68
	[line]
		16
		0
		3
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		2
		
		0
		1
		1
		0
		2
		0
		0
	[nfmt]
		272
		1
		2
		.
		,
		$
	Body Text
	0
	0
[tag]
	Chead
	0
	[fnt]
		Arial
		180
		0
		16385
	[algn]
		1
		3
		0
		0
		0
	[spc]
		40
		200
		4
		100
		0
		3
		100
	[brk]
		68
	[line]
		16
		0
		3
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		3
		
		0
		1
		1
		0
		2
		0
		0
	[nfmt]
		272
		1
		2
		.
		,
		$
	Body Text
	0
	0
[tag]
	2nd lev para
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		600
		0
		0
	[spc]
		40
		200
		4
		19
		60
		3
		100
	[brk]
		4
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		
		0
		1
		1
		0
		0
		0
		0
	[nfmt]
		272
		1
		2
		.
		,
		$
	2nd lev para
	0
	0
[tag]
	See also prnt
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		0
		0
	[spc]
		24
		200
		4
		19
		60
		3
		100
	[brk]
		36
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		
		0
		1
		1
		0
		0
		0
		0
	[nfmt]
		280
		1
		2
		.
		,
		$
	See also prnt
	5
	1
	480
	1
	960
	1
	1440
	1
	1920
	1
	2400
	0
[tag]
	Book art
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		0
		0
	[spc]
		24
		200
		4
		19
		60
		3
		100
	[brk]
		36
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		
		0
		1
		1
		0
		0
		0
		0
	[nfmt]
		280
		1
		2
		.
		,
		$
	Book art
	5
	1
	480
	1
	960
	1
	1440
	1
	1920
	1
	2400
	0
[tag]
	Callout text
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		0
		0
	[spc]
		24
		200
		4
		19
		60
		3
		100
	[brk]
		36
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		
		0
		1
		1
		0
		0
		0
		0
	[nfmt]
		280
		1
		2
		.
		,
		$
	Callout text
	5
	1
	480
	1
	960
	1
	1440
	1
	1920
	1
	2400
	0
[tag]
	Figure title
	0
	[fnt]
		Arial
		180
		0
		16385
	[algn]
		1
		3
		0
		0
		0
	[spc]
		40
		200
		4
		40
		60
		3
		100
	[brk]
		4
	[line]
		16
		0
		3
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		
		0
		1
		1
		0
		0
		0
		0
	[nfmt]
		272
		1
		2
		.
		,
		$
	Figure title
	0
	0
[tag]
	Chapter title
	0
	[fnt]
		Arial
		280
		0
		16385
	[algn]
		1
		3
		0
		0
		0
	[spc]
		24
		300
		4
		19
		60
		3
		100
	[brk]
		36
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		
		0
		1
		1
		0
		2
		0
		0
	[nfmt]
		280
		1
		2
		.
		,
		$
	Chapter title
	5
	1
	480
	1
	960
	1
	1440
	1
	1920
	1
	2400
	0
[tag]
	1st pg foot
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		0
		0
	[spc]
		24
		200
		4
		19
		60
		3
		100
	[brk]
		36
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		
		0
		1
		1
		0
		0
		0
		0
	[nfmt]
		280
		1
		2
		.
		,
		$
	1st pg foot
	5
	1
	480
	1
	960
	1
	1440
	1
	1920
	1
	2400
	0
[tag]
	Right pg foot
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		0
		0
	[spc]
		24
		200
		4
		19
		60
		3
		100
	[brk]
		36
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		
		0
		1
		1
		0
		0
		0
		0
	[nfmt]
		280
		1
		2
		.
		,
		$
	Right pg foot
	5
	1
	480
	1
	960
	1
	1440
	1
	1920
	1
	2400
	0
[tag]
	Left pg foot
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		0
		0
	[spc]
		24
		200
		4
		19
		60
		3
		100
	[brk]
		36
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		
		0
		1
		1
		0
		0
		0
		0
	[nfmt]
		280
		1
		2
		.
		,
		$
	Left pg foot
	5
	1
	480
	1
	960
	1
	1440
	1
	1920
	1
	2400
	0
[tag]
	Table title
	0
	[fnt]
		Arial
		180
		0
		16385
	[algn]
		1
		3
		0
		0
		0
	[spc]
		40
		200
		4
		60
		0
		3
		100
	[brk]
		4
	[line]
		16
		0
		3
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		7
		
		0
		1
		1
		0
		0
		0
		0
	[nfmt]
		272
		1
		2
		.
		,
		$
	Table title
	0
	0
[tag]
	Table col hd
	0
	[fnt]
		Arial
		180
		0
		16385
	[algn]
		1
		3
		0
		0
		0
	[spc]
		40
		200
		4
		100
		0
		3
		100
	[brk]
		4
	[line]
		10
		0
		3
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		6
		
		0
		1
		1
		0
		0
		0
		0
	[nfmt]
		256
		1
		0
		
		
		
	Table col hd
	0
	0
[tag]
	Table Text
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		1
		0
		0
		0
	[spc]
		40
		200
		4
		79
		0
		3
		100
	[brk]
		4
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		
		0
		1
		1
		0
		0
		0
		0
	[nfmt]
		256
		1
		0
		
		
		
	Table Text
	0
	0
[tag]
	See also hlp
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		0
		0
	[spc]
		40
		40
		4
		180
		0
		3
		100
	[brk]
		96
	[line]
		9
		0
		3
		0
		1
		1
		1
		70
		10
		1
	[spec]
		0
		0
		
		0
		1
		1
		0
		0
		0
		0
	[nfmt]
		280
		1
		2
		.
		,
		$
	See also btn
	0
	120
[tag]
	See also btn
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		0
		240
	[spc]
		24
		200
		4
		0
		60
		3
		100
	[brk]
		36
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		
		0
		1
		1
		0
		0
		0
		0
	[nfmt]
		280
		1
		2
		.
		,
		$
	See also btn
	5
	1
	480
	1
	960
	1
	1440
	1
	1920
	1
	2400
	0
[tag]
	Indnt caution
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		300
		720
		0
	[spc]
		40
		200
		4
		19
		60
		3
		100
	[brk]
		4
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		Caution
		0
		3
		1
		1
		0
		0
		0
	[nfmt]
		256
		1
		2
		.
		,
		$
	Indnt caution
	0
	0
[tag]
	Indnt tip
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		300
		324
		0
	[spc]
		24
		200
		4
		19
		60
		3
		100
	[brk]
		36
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		Tip
		0
		3
		1
		1
		0
		0
		0
	[nfmt]
		280
		1
		2
		.
		,
		$
	Indnt tip
	5
	1
	480
	1
	960
	1
	1440
	1
	1920
	1
	2400
	0
[tag]
	Indnt note
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		300
		468
		0
	[spc]
		40
		200
		4
		19
		60
		3
		100
	[brk]
		4
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		Note
		0
		3
		1
		1
		0
		0
		0
	[nfmt]
		256
		1
		2
		.
		,
		$
	Indnt note
	0
	0
[tag]
	Caution
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		720
		0
	[spc]
		40
		200
		4
		19
		60
		3
		100
	[brk]
		4
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		Caution
		0
		3
		1
		1
		0
		0
		0
	[nfmt]
		256
		1
		2
		.
		,
		$
	Caution
	0
	0
[tag]
	Tip
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		324
		0
	[spc]
		40
		200
		4
		19
		60
		3
		100
	[brk]
		4
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		Tip
		0
		3
		1
		1
		0
		0
		0
	[nfmt]
		256
		1
		2
		.
		,
		$
	Tip
	0
	0
[tag]
	Note
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		468
		0
	[spc]
		40
		200
		4
		19
		60
		3
		100
	[brk]
		4
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		Note
		0
		3
		1
		1
		0
		0
		0
	[nfmt]
		256
		1
		2
		.
		,
		$
	Note
	0
	0
[tag]
	Mono
	0
	[fnt]
		Courier New
		180
		0
		32768
	[algn]
		1
		3
		0
		0
		0
	[spc]
		24
		200
		4
		19
		60
		3
		100
	[brk]
		32
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		
		0
		1
		1
		0
		0
		0
		0
	[nfmt]
		280
		1
		2
		.
		,
		$
	Mono
	15
	1
	480
	1
	960
	1
	1440
	1
	1920
	1
	2400
	1
	2880
	1
	3360
	1
	3840
	1
	4320
	1
	4800
	1
	5280
	1
	5760
	1
	6240
	1
	6720
	1
	7200
	0
[tag]
	Indnt mono
	0
	[fnt]
		Courier New
		180
		0
		32768
	[algn]
		1
		3
		300
		0
		0
	[spc]
		24
		200
		4
		19
		60
		3
		100
	[brk]
		32
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		
		0
		1
		1
		0
		0
		0
		0
	[nfmt]
		280
		1
		2
		.
		,
		$
	Indnt mono
	15
	1
	480
	1
	960
	1
	1440
	1
	1920
	1
	2400
	1
	2880
	1
	3360
	1
	3840
	1
	4320
	1
	4800
	1
	5280
	1
	5760
	1
	6240
	1
	6720
	1
	7200
	0
[tag]
	Parameter
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		0
		0
	[spc]
		24
		200
		4
		19
		0
		3
		100
	[brk]
		36
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		
		0
		1
		1
		0
		0
		0
		0
	[nfmt]
		280
		1
		2
		.
		,
		$
	Parameter
	5
	1
	480
	1
	960
	1
	1440
	1
	1920
	1
	2400
	0
[tag]
	Formula
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		0
		0
	[spc]
		24
		200
		4
		19
		60
		3
		100
	[brk]
		36
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		
		0
		1
		1
		0
		0
		0
		0
	[nfmt]
		280
		1
		2
		.
		,
		$
	Formula
	0
	0
[tag]
	Browse
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		139
		139
	[spc]
		24
		200
		4
		0
		0
		3
		100
	[brk]
		4
	[line]
		16
		0
		3
		0
		1
		2
		2
		20
		20
		1
	[spec]
		0
		0
		+
		0
		3
		1
		256
		1
		0
		0
	[nfmt]
		280
		1
		3
		.
		,
		$
	Browse
	0
	0
[tag]
	Keyword
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		139
		139
	[spc]
		24
		200
		4
		0
		0
		3
		100
	[brk]
		4
	[line]
		16
		0
		3
		0
		1
		2
		2
		20
		20
		1
	[spec]
		0
		0
		K
		0
		3
		1
		256
		1
		0
		0
	[nfmt]
		280
		1
		3
		.
		,
		$
	Keyword
	0
	0
[tag]
	Context
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		139
		139
	[spc]
		24
		200
		4
		0
		0
		3
		100
	[brk]
		4
	[line]
		16
		0
		3
		0
		1
		2
		2
		20
		20
		1
	[spec]
		0
		0
		#
		0
		3
		1
		256
		1
		0
		0
	[nfmt]
		280
		1
		3
		.
		,
		$
	Context
	0
	0
[tag]
	Title
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		139
		139
	[spc]
		24
		200
		4
		0
		0
		3
		100
	[brk]
		4
	[line]
		16
		0
		3
		0
		1
		2
		2
		20
		20
		1
	[spec]
		0
		0
		$
		0
		3
		1
		256
		1
		0
		0
	[nfmt]
		280
		1
		3
		.
		,
		$
	Title
	0
	0
[tag]
	Macros
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		139
		139
	[spc]
		24
		200
		4
		0
		0
		3
		100
	[brk]
		4
	[line]
		16
		0
		3
		0
		1
		2
		2
		20
		20
		1
	[spec]
		0
		0
		!
		0
		3
		1
		256
		1
		0
		0
	[nfmt]
		280
		1
		3
		.
		,
		$
	Macros
	0
	0
[tag]
	Footnote
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		244
		0
	[spc]
		40
		2400
		3
		0
		0
		1
		100
	[brk]
		4
	[line]
		16
		0
		3
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		
		0
		1
		1
		256
		0
		0
		0
	[nfmt]
		280
		1
		2
		.
		,
		$
	Footnote
	0
	0
[tag]
	Alink
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		139
		139
	[spc]
		24
		200
		4
		0
		0
		3
		100
	[brk]
		4
	[line]
		16
		0
		3
		0
		1
		2
		2
		20
		20
		1
	[spec]
		0
		0
		A
		0
		3
		1
		256
		1
		0
		0
	[nfmt]
		280
		1
		3
		.
		,
		$
	Alink
	0
	0
[tag]
	Butnbar
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		0
		0
	[spc]
		40
		200
		4
		0
		0
		3
		100
	[brk]
		48
	[line]
		16
		0
		3
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		\li-140 
		0
		1
		1
		0
		0
		0
		0
	[nfmt]
		272
		1
		2
		.
		,
		wr
	Butnbar
	0
	0
[tag]
	Window
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		139
		139
	[spc]
		24
		200
		4
		0
		0
		3
		100
	[brk]
		4
	[line]
		16
		0
		3
		0
		1
		2
		2
		20
		20
		1
	[spec]
		0
		0
		>
		0
		3
		1
		256
		1
		0
		0
	[nfmt]
		280
		1
		3
		.
		,
		$
	Window
	0
	0
[tag]
	Win95 macros
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		139
		139
	[spc]
		24
		200
		4
		0
		0
		3
		100
	[brk]
		4
	[line]
		16
		0
		3
		0
		1
		2
		2
		20
		20
		1
	[spec]
		0
		0
		W
		0
		3
		1
		256
		1
		0
		0
	[nfmt]
		280
		1
		3
		.
		,
		$
	Win95 macros
	0
	0
[tag]
	Win31 macros
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		139
		139
	[spc]
		24
		200
		4
		0
		0
		3
		100
	[brk]
		4
	[line]
		16
		0
		3
		0
		1
		2
		2
		20
		20
		1
	[spec]
		0
		0
		X
		0
		3
		1
		256
		1
		0
		0
	[nfmt]
		280
		1
		3
		.
		,
		$
	Win31 macros
	0
	0
[tag]
	Build tag
	0
	[fnt]
		Arial
		180
		0
		16384
	[algn]
		1
		3
		0
		139
		139
	[spc]
		24
		200
		4
		0
		0
		3
		100
	[brk]
		4
	[line]
		16
		0
		3
		0
		1
		2
		2
		20
		20
		1
	[spec]
		0
		0
		*
		0
		3
		1
		256
		1
		0
		0
	[nfmt]
		280
		1
		3
		.
		,
		$
	Build tag
	0
	0
[tag]
	_COND_IF
	0
	[fnt]
		Arial
		240
		255
		16385
	[algn]
		1
		3
		0
		0
		0
	[spc]
		24
		200
		4
		100
		0
		3
		100
	[brk]
		100
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		IF
		0
		1
		1
		0
		0
		0
		0
	[nfmt]
		280
		1
		2
		.
		,
		$
	Body Text
	5
	1
	480
	1
	960
	1
	1440
	1
	1920
	1
	2400
	0
[tag]
	_COND_ELSE
	0
	[fnt]
		Arial
		240
		255
		16385
	[algn]
		1
		3
		0
		0
		0
	[spc]
		24
		200
		4
		100
		0
		3
		100
	[brk]
		100
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		ELSE
		0
		1
		1
		0
		0
		0
		0
	[nfmt]
		280
		1
		2
		.
		,
		$
	Body Text
	5
	1
	480
	1
	960
	1
	1440
	1
	1920
	1
	2400
	0
[tag]
	_COND_ENDIF
	0
	[fnt]
		Arial
		240
		255
		16385
	[algn]
		1
		3
		0
		0
		0
	[spc]
		24
		200
		4
		100
		0
		3
		100
	[brk]
		100
	[line]
		8
		0
		1
		0
		1
		1
		1
		10
		10
		1
	[spec]
		0
		0
		ENDIF
		0
		1
		1
		0
		0
		0
		0
	[nfmt]
		280
		1
		2
		.
		,
		$
	Body Text
	5
	1
	480
	1
	960
	1
	1440
	1
	1920
	1
	2400
	0
[lay]
	Standard
	3079
	[rght]
		12960
		10166
		1
		720
		1200
		3
		960
		960
		0
		1
		0
		1
		0
		2
		1
		720
		9206
		1
		1
		3120
	[lft]
		12960
		10166
		1
		960
		1200
		3
		960
		720
		0
		1
		0
		1
		0
		2
		1
		960
		9446
		1
		1
		3120
	[hlft]
	[lyfrm]
		1
		3008
		0
		0
		10166
		960
		0
		1
		3
		1 0 0 0 0 0 0
		0
		0
		3
	[frmlay]
		960
		10166
		1
		960
		180
		3
		0
		720
		0
		1
		0
		1
		1
		0
		1
		960
		9446
		1
		2
		4674
	[txt]
>
	[hrght]
	[lyfrm]
		1
		11200
		0
		0
		10166
		960
		0
		1
		3
		1 0 0 0 0 0 0
		0
		0
		1
	[frmlay]
		960
		10166
		1
		720
		180
		3
		0
		960
		0
		1
		0
		1
		1
		0
		1
		720
		9206
		1
		2
		4674
	[txt]
>
	[flft]
	[lyfrm]
		1
		5056
		0
		11760
		10166
		12960
		0
		1
		3
		1 0 0 0 0 0 0
		0
		0
		4
	[frmlay]
		12960
		10166
		1
		960
		480
		3
		11940
		720
		0
		1
		0
		1
		1
		0
		1
		960
		9446
		1
		3
		9900
	[txt]
>
	[frght]
	[lyfrm]
		1
		13248
		0
		11760
		10166
		12960
		0
		1
		3
		1 0 0 0 0 0 0
		0
		0
		2
	[frmlay]
		12960
		10166
		1
		720
		480
		3
		11940
		960
		0
		1
		0
		1
		1
		0
		1
		720
		9206
		1
		3
		9900
	[txt]
@1st pg foot@ Lotus Confidential                                            Chapter 1: Introduction to Notes Development 
<:P19999,0,1->

>
[elay]
[l1]
	0
[pg]
	18
	26 0 38 0 0 0 0 200 65535 Standard	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 1 0 0 0 0
	54 89 30 0 0 0 0 239 65535 Standard	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 1 0 0 0 0
	84 0 27 0 0 0 0 239 65535 Standard	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 1 0 0 0 0
	110 198 95 0 0 0 0 200 65535 Standard	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 1 0 0 0 0
	130 0 44 32 0 0 0 200 65535 Standard	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 1 0 0 0 0
	161 0 37 32 0 0 0 200 65535 Standard	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 1 0 0 0 0
	182 0 60 0 0 0 0 200 65535 Standard	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 1 0 0 0 0
	212 102 100 32 0 0 0 200 65535 Standard	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 1 0 0 0 0
	233 94 104 32 0 0 0 65535 65535 Standard	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 1 0 0 0 0
	255 94 7 32 0 0 0 200 65535 Standard	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 1 0 0 0 0
	280 91 51 0 0 0 0 200 65535 Standard	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 1 0 0 0 0
	300 99 102 0 0 0 0 65535 65535 Standard	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 1 0 0 0 0
	322 0 16 0 0 0 0 200 65535 Standard	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 1 0 0 0 0
	354 0 52 0 0 0 0 200 65535 Standard	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 1 0 0 0 0
	388 0 18 0 0 0 0 200 65535 Standard	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 1 0 0 0 0
	419 0 82 0 0 0 0 200 65535 Standard	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 1 0 0 0 0
	451 0 18 0 0 0 0 200 65535 Standard	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 1 0 0 0 0
	474 0 0 1025 0 0 0 200 65535 Standard	65535 0 0	0 0 0 0 0 0 0 65535 0 0 65535 1 0 0 0 0
[edoc]
@Ahead@<+@><:s><:I0,0,0,0><:S+-1><:#332,8486><:f280,,><+!>Chapter 1   Introduction to <-!><:f><+!><:f280,,>Notes 
<-!><+!>Development<-!><:f>

<:s><:I0,0,0,0><:S+-1><:#422,8486><:X8,1;Index "Introduction" # "to Notes development"><:X8,1;Index "Development" # "introduction to Notes">Lotus Notes allows people to access, track, share, and organize information in ways never before possible, even if they are only occasionally connected
 to a network.

<:s><:I0,0,0,0><:S+-1>A<:h<*&>
@Left pg foot@<:P19999,0,1->  Application Developer's Guide                                                                      Lotus Confidential

>
<:h<**>
@Right pg foot@<+A>Lotus Confidential                                                                   Introduction to Notes Development  
<:P19999,0,1->

>
s a Notes application developer, you help people manage the collection and flow of information by designing applications that help them complete a business process electronically. To make your job easier, Notes ships with a set of pre</m>designed applicatio
ns (templates and example databases) that require little to no customization.

@Ahead@<+@><:s><:I0,0,0,0><:S+-1><:R1,2,1,360,1,720,><:#269,8486>About Notes applications

<+@><:s><:I0,0,0,0><:S+-1><:R1,2,1,360,1,720,><:#211,8486>A Notes application can be one of, or a mix of, five basic types.

@Bullet@<:s><:R1,2,1,360,1,720,><:#800,8486><+">Approval applications<-"> provide an electronic method for reviewing information or approving requests. Such applications often use mail routing, automated reminders, tracking features, and sets of actions that are based on different conditions. Approva
l applications require active participation by the people who are reviewers or approvers. 

@Bullet@<:s><:R1,2,1,360,1,720,><:#600,8486><+"><:X8,1;Index "Broadcast application" #><:f,,>Broadcast applications<-"> 
<:f>keep people updated with news items they need for their work. Information is often disseminated through mail messages.<:f,,> Such applications 
<:f><:f,,>are available to a large audience and contain information<:f><:f,,> that is usually time</m>critical but doesn't change<:f>. 

@Bullet@<:s><:R1,2,1,360,1,720,><:#600,8486><:X8,1;Index "Discussion application" #><:X8,1;Index "Application" # "Discussion"><:f,,><+">Discussion applications<-"> support 
<:f><:f,,>group communication. They are <:f><:f,,>designed to improve upon<:f><:f,,> 
<:f><:f,,>face-to-face meetings <:f><:f,,>by encouraging <:f><:f,,>people's ideas and responses without forcing them to be restricted to 
<:f><:f,,>a particular location or time.<:f>

@Bullet@<:s><:R1,2,1,360,1,720,><:#200,8486><+"><:X8,1;Index "Reference application" #><:X8,1;Index "Application" # "reference"><:f,,>Reference applications<-"> 
<:f><:f,,>provide a library of shared information <:f><:f,,>that can be updated as necessary.<:f>

@Bullet@<:s><:R1,2,1,360,1,720,><:#600,8486><:X8,1;Index "Tracking application" #><:X8,1;Index "Application" # "tracking"><:f,,><+">Tracking applications<-"> 
<:f><:f,,>are designed to replace a paper-based activity<:f><:f,,> by an electronic one in which 
<:f><:f,,>users contribute to<:f><:f,,> the activity<:f><:f,,>, <:f><:f,,>keep track of progress<:f><:f,,>, or produce reports<:f><:f,,>. Such applications 
<:f><:f,,>usually <:f><:f,,>involve <:f><:f,,>many active users, sometimes from different workgroups<:f><:f,,>.<:f>

<:s><:R1,2,1,360,1,720,><:#400,8486><+"><:f,,>Workflow<-"> features<:f><:f,,> <:f><:f,,>can be added to any type of application to automate 
<:f><:f,,>routine tasks, such as routing forms, sending reminders, requesting approvals, and running scheduled batch processes.<:f>

<:s><:R1,2,1,360,1,720,><:#600,8486>An application can include features of more than one type. For example, a reference database about company policies can have a discussion-like format  to allow employees to add suggestions or comments. 
<:X8,1;Index "Application" # "workflow"><:X8,1;Index "Workflow application" #><-">

@See also hlp@<:s><:R1,2,1,360,1,720,><:#110,8486><:f,,>

@See also btn@<:s><:R1,2,1,360,1,720,><:#200,8486><-#><-#><-#><+)>

@See also btn@<:R1,2,1,360,1,720,><:#200,8486><+)>{bmc 1details.bmp} See examples<-)><+*>H_EXAMPLES:_ABOUT_NOTES_APPLICATIONS<-*>

@Crossref@<:R1,2,1,360,1,720,><:#200,8486><+)>About the structure of an application<-)><+*>H_ABOUT_THE_STRUCTURE_OF_AN_APPLICATION<-*>

@See also btn@<:s><:R1,2,1,360,1,720,><:#200,8486><-#><-#>

@Bhead title@<:s><:R><:#220,8486><-#>Examples: About Notes applications

@Chead title@<:#200,8486>TO BE UPDATED WITH V4 TEMPLATES AND EXAMPLES++

@Chead title@<:s><:#200,8486>Approval applications

<:s><:S+239><:#239,8486>Templates of this type are:

<:s><:S+239><:#239,8486>ARE THERE ANY??

<:s><:S+239><:#239,8486>Notes example applications of this type are:

@Bullet@<:s><:#200,8486>Business Card Request  and Lookup Keyword Library

@Bullet@<:s><:#200,8486>Travel Authorizations 

@Bullet@<:s><:#200,8486>Purchase Requisition application suite

<:s><:S+239><:#239,8486>Customized applications you could create include:

@Bullet@<:s><:S+239><:#717,8486>Purchasing Requests lets users request purchases electronically, mail them to their managers for approval, and then routes approved requests to Purchasing where purchase orders are written and tracked.

@Bullet@<:s><:#400,8486>Expense Reports keeps track of employee's expenses and routes reimbursement requests to the employee's manager for approval, and then to Accounts Payable for payment.

@Bullet@<:s><:#400,8486>Marketing Plans solicits all department managers' comments about each product's marketing plan and ensures managers' signoff before announcing the plan.

@Bullet@<:s><:S+239><:#239,8486>Loan Approvals routes a loan application to the appropriate managers for approval.

@Bullet@<:s><:S+239><:#478,8486>Insurance Claims Processing routes new claims to the appropriate regional manager for approval and tracks the status of each claim.

@Chead title@<:s><:#200,8486>Broadcast applications

<:s><:S+239><:#239,8486>Templates of this type are:

@Bullet@<:s><:S+239><:#239,8486>News

<:s><:S+239><:#239,8486>Notes example applications of this type are:

@Bullet@<:s><:S+239><:#239,8486>Notes News

<:s><:S+239><:#239,8486>Customized applications you could create include:

@Bullet@<:s><:S+239><:#478,8486>Industry News provides up</m>to</m>date information about a specific industry. Industry news feeds from external sources supply the information, which is available for later reference and research.

@Bullet@<:s><:S+239><:#239,8486>Meeting Agendas and Minutes records group ideas for regularly scheduled meetings.

@Bullet@<:s><:S+239><:#239,8486>Newsletters advises employees of company happenings.

@Bullet@<:s><:S+239><:#478,8486>Conference Room Schedule stores conference room reservations and automatically sends meeting reminders to attendees.

@Chead title@<:s><:#200,8486>Discussion applications

<:s><:S+239><:#239,8486>Templates of this type are:

@Bullet@<:s><:S+239><:#239,8486>Discussion

@Bullet@<:s><:S+239><:#239,8486>Team Issues

<:s><:S+239><:#239,8486>Notes example applications of this type are:

@Bullet@<:s><:S+239><:#239,8486>Customer Suggestions (part of the Customer Service application)

@Bullet@<:s><:S+239><:#239,8486>Product Design Problems (part of the Customer Service application)

@Bullet@<:s><:S+239><:#239,8486>Support Conference

<:s><:S+239><:#239,8486>Customized applications you could create include:

@Bullet@<:s><:S+239><:#239,8486>Brainstorming Database stores ideas on a variety of topics.

@Bullet@<:s><:S+239><:#239,8486>Feedback or Opinion Database lets users respond to any topic.

@Bullet@<:s><:S+239><:#478,8486>Suggestion Box allows employees to make suggestions about company improvements and check any actions taken as a result.

@Bullet@<:s><:S+239><:#239,8486>MORE IDEAS?? -- ADD IDEAS THAT INCORPORATE WORKFLOW ??

@Chead title@<:s><:#200,8486>Reference applications

<:s><:S+239><:#239,8486>Templates of this type are:

@Bullet@<:s><:S+239><:#239,8486>Correspondence

@Bullet@<:s><:S+239><:#239,8486>Custom Mail Forms

@Bullet@<:s><:S+239><:#239,8486>Document Library

@Bullet@<:s><:S+239><:#239,8486>Phone Book

@Bullet@<:s><:S+239><:#239,8486>Reference Documents

<:s><:S+239><:#239,8486>Notes example applications of this type are:

@Bullet@<:s><:S+239><:#239,8486>Contract Library

@Bullet@<:s><:S+239><:#239,8486>Data Dictionary (part of Customer Service application)

@Bullet@<:s><:S+239><:#239,8486>Template & Example Card Catalog

@Bullet@<:s><:S+239><:#239,8486>Electronic Library

<:s><:S+239><:#239,8486>Customized applications you could create include:

@Bullet@<:s><:S+239><:#239,8486>Policies and Procedures Handbook maintains an up</m>to</m>date record of company policy.

@Bullet@<:s><:S+239><:#239,8486>Market Research stores marketing data from a variety of sources.

@Bullet@<:s><:S+239><:#239,8486>Software Code Library stores software routines that are shared among developers.

@Bullet@<:s><:S+239><:#478,8486>Customer Support records customer questions and preferred answers. The documents are categorized, and the database is used as an interactive customer service tool. 

@Bullet@<:s><:S+239><:#717,8486>Compensation & Benefits stores all employee compensation information; an automatic process (called an agent) updates all employee records on a predetermined schedule, calculates raises, and sends the employee's new salary amount to the manager.

@Bullet@<:s><:S+239><:#717,8486>Employee Reviews keeps a history of employees</R> performance reviews, sends reminders to managers about overdue reviews, and is used by the Compensation & Benefits database when it calculates raises

@Chead title@<:s><:#200,8486>Tracking applications

<:s><:S+239><:#239,8486>Templates of this type are:

@Bullet@<:s><:S+239><:#239,8486>Customer Tracking

@Bullet@<:s><:S+239><:#239,8486>Meeting Tracking

@Bullet@<:s><:S+239><:#239,8486>Reservation Scheduler

@Bullet@<:s><:S+239><:#239,8486>Service Request Tracking

@Bullet@<:s><:S+239><:#239,8486>Things to Do

<:s><:S+239><:#239,8486>Notes example applications of this type are:

@Bullet@<:s><:S+239><:#239,8486>Call Tracking Database (part of the Customer Service application)

@Bullet@<:s><:S+239><:#239,8486>Wholesale Customer Tracking

@Bullet@<:s><:S+239><:#239,8486>Call Tracking

@Bullet@<:s><:S+239><:#239,8486>Travel Authorizations

@Bullet@<:s><:S+239><:#239,8486>Business Card Request

@Bullet@<:s><:S+239><:#239,8486>Purchase Requisition application suite

<:s><:S+239><:#239,8486>Customized applications you could create include:

@Bullet@<:s><:S+239><:#478,8486>Event Planning tracks deliverables, dates, and assignments for a specific event and generates reminders for overdue items.

@Bullet@<:s><:S+239><:#239,8486>Sales Account Tracking keeps a record of accounts</R> relationships with your business.

@Bullet@<:s><:S+239><:#478,8486>Resume Tracking keeps tabs on incoming resumes and the status of interviews generated by resumes.

@Bullet@<:s><:S+239><:#239,8486>Project Status Reports tracks the ongoing progress of projects.

@Bullet@<:s><:S+239><:#239,8486>Service Tracking records the number and types of service calls.

@Bullet@<:s><:S+239><:#478,8486>Inventory Supply Monitor tracks incoming and outgoing inventory and generates new purchase orders when the inventory drops to a certain level.

@Bullet@<:s><:S+239><:#478,8486>Credit and Collections Management tracks outstanding loans and payments received, and flags accounts that are overdue.

@See also hlp@<:s><:R1,2,1,360,1,720,><:#110,8486>

@See also btn@<:s><:R1,2,1,360,1,720,><:#200,8486><+)>

@Crossref@<:R1,2,1,360,1,720,><:#200,8486><+)>Application templates<-)><+*>H_APPLICATION_TEMPLATES<-*>

@Crossref@<:R1,2,1,360,1,720,><:#200,8486><+)>Notes example databases<-)><+*>H_NOTES_EXAMPLE_DATABASES<-*>

@Bhead title@<:s><:R1,2,1,360,1,720,><:#220,8486>About the advantages of developing in Notes

<:s><:I0,0,0,0><:S+-1><:R1,2,1,360,1,720,><:#211,8486>Developing applications in Notes offers many advantages.

@Bullet@<:s><:R1,2,1,360,1,720,><:#200,8486><+!>Notes provides a standard interface for users<-!>

@1st lev para@<:s><:R><:#800,8486>All Notes databases are unified by the Notes workstation user interface. Users need only one set of menu commands and editing keystrokes whenever they work in Notes. Once users learn to read and write documents in one database, they can read and write docum
ents in any Notes database, even if the database design is new. 

@1st lev para@<:s><:#400,8486>To promote even greater consistency among databases, you can distribute standard designs (called design templates) that easily propagate design changes as needed to users</R> databases.

@Bullet@<:s><:#200,8486><+!>Notes runs on Windows, OS/2, Macintosh, and UNIX workstations<-!>

@1st lev para@<+@><:s><:#400,8486>Anyone with a Notes workstation can access and create information, no matter which operating system is on the machine.

@Bullet@<:s><:#200,8486><+!>Notes allows multiple users to access the same data<-!>

@1st lev para@<:s><:#1000,8486>Because most Notes databases reside on Notes servers rather than on individual personal computers, users can access the same database at the same time. As soon as one user updates a document and saves changes, the new information is accessible to other user
s of that database. While a user is updating a document, another user can open the same document and also update it because Notes can store multiple versions of the same document. 

@1st lev para@<:s><:#1200,8486>Even when users are in different buildings, cities, or countries, they can have access to identical information. Replica copies of a database can be placed on several Notes servers, so users in one location can see changes made by users at another location 
as soon as the two servers exchange updates. For example, a user in the Toronto office can read about a new customer soon after a user in Detroit adds that information. Replication is supported in both multiple</m>LAN and WAN environments.

@Bullet@<:s><:#200,8486><+!>Notes users do not need a network<-!>

@1st lev para@<:s><:#600,8486>Notes makes it easy for users who aren't connected to a network to dial up to servers through modems. Whether they are at home, in a hotel, or in a branch office, users can contribute and have access to the same information as their colleagues who are conne
cted to the network.

@Bullet@<:s><:#200,8486><+!>Access to information can be controlled<-!>

@1st lev para@<:s><:#1200,8486>Notes provides several levels and types of security across organizations, offices, and workgroups as well as on a per server, database, document, or field basis. For example, you can let all users at your organization read and write entries in the company p
hone book, but only allow members of the product development team to read and contribute to their workgroup's discussion database. Data can also be encrypted when it is routed or stored and then decrypted only by those users who have the correct encryption 
key. 

@Bullet@<:s><:#200,8486><+!>Notes applications can use electronic mail<-!>

@1st lev para@<:#1000,8486>Notes applications support electronic mail, so it's easy to design applications that route documents automatically to people or databases for approval, reminders, or status tracking. Notes can even route documents to cc:Mail</Y> and other VIM</m>compliant e
</m>mail products, and to Lotus SmartSuite</n> products<:f,,>.<:f><:f,,> In addition, a Notes user can 
</S><:f><:f,,>mail-forward</T><:f><:f,,> any Notes document through the Notes mail system. 
<:f>

@1st lev para@<:s><:#200,8486><:f,,>Electronic mail is supported in both multiple</m>LAN and WAN environments.<:f>

@Bullet@<:s><:#200,8486><+!>Notes applications can automate workflow<-!>

@1st lev para@<:s><:#200,8486>You can combine many Notes features to build a powerful workflow application that can

@Indnt bullet@<:s><:#200,8486>Automatically route a document or notifications to the next specified user or approver

@2nd lev para@<:s><:#800,8486>You can name the approvers in advance for all documents created with a particular form, or have users name them on a per-document basis and then have those forms routed to the next approver. Documents can also be routed differently depending on conditions, 
such as when a field's value is greater than a particular amount or when a user specifies an additional approver.

@Indnt bullet@<:s><:#200,8486>Take different actions, depending on conditions

@2nd lev para@<:s><:#400,8486>If a customer service representative escalates a call to a different representative, Notes can notify all appropriate parties and reclassify the call report.

@Indnt bullet@<:s><:#200,8486>Allow management to track business processes more closely

@2nd lev para@<:#400,8486>Managers can be notified of project status automatically or can generate reports about task durations or resource allocation.

@Indnt bullet@<:#200,8486><-">Route other product's files and use Notes for storage, tracking, and organization of files

@2nd lev para@<:s><:#800,8486>Notes can launch other products automatically to allow easy viewing and editing of another product's file. By adding routing actions to the file, users can also send their revisions to others for review and approval. The Notes database can keep track of and
 display information about the file. 

@Bullet@<:s><:#200,8486><+!>Notes can grow as your company does<-!>

@1st lev para@<+@><:s><:#600,8486>Notes is scaleable from the smallest office or department to the largest multinational company--just keep adding Notes users and servers as you grow. In addition to English, Notes is available in many other languages. 

@Bullet@<:s><:#200,8486><+!>Notes applications can use external data<-!>

@1st lev para@<:s><:#400,8486>In addition to its import and export features, Notes provides several mechanisms for accessing external data from other desktop applications, database products, or mainframe systems:

@Indnt bullet@<:s><:#200,8486>OLE (Object Linking and Embedding)

@Indnt bullet@<:s><:#200,8486>LEL (Link, Embed, and Launch</m>to</m>edit)

@Indnt bullet@<:s><:#200,8486>Subscribe

@Indnt bullet@<:s><:#200,8486>ODBC (Open Database Connectivity) database drivers

@Indnt bullet@<:s><:#400,8486>@DbCommand, @DbColumn, @DbLookup, the Notes @functions that look up data in external databases 

@Indnt bullet@<:s><:#200,8486>@MailSend, the Notes @function that sends mail to other products

@Indnt bullet@<:s><:#400,8486>@DDEInitiate, @DDEExecute, @DDEPoke, @DDETerminate, the Notes @functions that initiate a DDE conversation with another product

@Indnt bullet@<:s><:#200,8486>Direct launching of files attached to Notes documents

@Bullet@<:s><:#200,8486><+!>Notes applications can connect directly to other Lotus products<-!>

@1st lev para@<:s><:#400,8486>Notes applications can use these other Lotus</n> products as part of their design, through the use of objects, and exchangeable Notes/FX fields, formulas, and programs:

@Indnt bullet@<+@><:s><:#200,8486>AmiPro</n>

@Indnt bullet@<+@><:s><:#200,8486>Approach</n>

@Indnt bullet@<+@><:#200,8486>cc:Mail</n>

@Indnt bullet@<+@><:s><:#200,8486>Freelance Graphics</n>

@Indnt bullet@<+@><:#200,8486>Improv</n>  <+!><+"> LEAVE IN??++<-"><-!>

@Indnt bullet@<+@><:s><:#200,8486>Lotus 1-2-3</n>

@Indnt bullet@<+@><:s><:#200,8486>Lotus Forms</Y>

@Indnt bullet@<+@><:s><:#200,8486>Phone Notes</Y>

@Indnt bullet@<+@><:s><:#200,8486>Video Notes</Y>

@Indnt bullet@<+@><:s><:#200,8486>Lotus Notes Document Imaging</Y> (LN:DI)

@Bullet@<:s><:#200,8486><+!>Lotus development tools can extend Notes capabilities<-!>

@1st lev para@<:#400,8486>If you are a programmer, you can use the Lotus Notes API or Lotus Notes VIP to expand what you can do with Notes.

@1st lev para@<:s><:R1,1,1,1080,><:#200,8486><+!>The Notes API<-!>

@1st lev para@<:s><:R><:#800,8486><:X8,6;Index "Extending Notes with other products" # "Notes API"><:X8,6;Index "Notes" # "API"><:X8,6;Index "API" # "for Notes">The Notes API lets you write a program that moves data in and out of Notes. The API accesses the Notes database layer, much as the
 Notes user interface itself accesses it. You can also use the API to access the server software, the Tools menu in the workstation software, and the File Types list in the File Export dialog box. 

@1st lev para@<:s><:#200,8486>You can write an API program to:

@Indnt bullet@<:s><:#200,8486>Extract external data, reformat it, and store it in Notes

@2nd lev para@<:s><:#200,8486>For example, you can retrieve information from SQL records.

@Indnt bullet@<:s><:#200,8486>Extract Notes data, reformat it, and store it in an external application

@2nd lev para@<:s><:#400,8486>For example, you can retrieve Notes workflow status data into a word processor or executive information management (EIS) system.

@Indnt bullet@<:s><:#200,8486>Add commands to the File - Tools menu

@2nd lev para@<:s><:#800,8486>For example, when a user chooses your new command, Notes can launch your program and pass user context information to it, such as which view is active, whether the user is editing a document, and which field contains the cursor. Your program can compute new
 values and enter them into Notes fields.

@Indnt bullet@<:s><:#200,8486>Implement server add-in tasks

@2nd lev para@<:s><:#600,8486>For example, you can implement a task that takes conditional actions beyond Notes background macro capabilities. A server add-in task functions as a daemon -- it has no user interface and runs in the background like other server tasks.

@Indnt bullet@<:s><:#200,8486>Create a custom file export format

@2nd lev para@<:s><:R1,1,1,1260,><:#400,8486>For example, when a user selects your new file type in the Notes File Export dialog box, Notes launches your program and exports Notes data to it.

@2nd lev para@<:s><:R1,2,1,360,1,720,><:#400,8486>For more information about the Notes API, see the Notes API R3.0.1 
<+">User's Guide.<-"> UPDATE FOR V4??

@1st lev para@<:s><:R1,1,1,1080,><:#200,8486><+!>Lotus Notes ViP<-!></Y>

@1st lev para@<:s><:R1,1,1,1080,><:#400,8486>Lotus Notes ViP is a visual programming system that can be purchased as an add-on product for use with Notes. 
<:X8,7;Index "Extending Notes with other products" # "Lotus Notes ViP"><:X8,7;Index "Notes" # "and Lotus Notes ViP"><:X8,7;Index "Lotus Notes ViP" # "and Notes">

@1st lev para@<:s><:R1,1,1,1080,><:#1000,8486>Lotus Notes ViP extends Lotus Notes in four key areas: query and update of Notes and corporate data, programmability via LotusScript, reporting and charting, and sophisticated GUI creation. With the Notes ViP data object, chart object, and report designer, 
you can build applications that connect to, retrieve, update, plot charts, and generate reports on data from Notes databases and other products. 

@1st lev para@<+@><:s><:R1,2,1,360,1,720,><:#200,8486>For more information about Notes ViP, see the Lotus Notes ViP <+">Application Developer's Guide<-">.

@Chead title@<:s><:R1,1,1,1080,><:#200,8486>Evaluating Notes as the application tool

<:R1,1,1,1080,><:#200,8486>NEED MORE INFO???++

<:s><:R1,1,1,1080,><:#400,8486>You may want to choose another application tool or combine Notes with another product if the application:

@Bullet@<+@><:s><:R><:#200,8486>Requires real-time access to data

@1st lev para@<:s><:#1000,8486><:f,,>If real-time access to data is required, <:f><:f,,>as it is 
<:f><:f,,>for <:f><:f,,>some <:f><:f,,>credit and order processing applications, consider using another application platform. 
<:f><:f,,>Developing applications in Notes is ideal when users <:f><:f,,>can tolerate a delay (30 to 60 minutes) for 
<:f><:f,,>updated information<:f><:f,,>, or if a database is maintained on a single server<:f><:f,,>. The Notes replication process makes multiple 
<:f><:f,,>copies of a database the same over time, but can't provide 
<:f><:f,,>updates to every location simultaneously<:f><:f,,>.<:f>

@Bullet@<+@><:s><:#200,8486>Involves many users accessing the system simultaneously -- STILL TRUE FOR V4??++

@Bullet@<+@><:s><:#200,8486>Requires sophisticated numerical calculations

@1st lev para@<:s><:#1400,8486><-"><:f,,>While Notes has many @functions to support mathematical calculations, it does not have the range of financial and mathematical functions found in spreadsheet or financial modeling programs. 
<:f>If an application requires sophisticated mathematical or financial calculation, consider using a Notes database to share the information once it has been calculated with some other software product. For example, you could create a budget in Lotus<:f,,> 
1</m>2</m>3<:f><:f,,>, and then embed the worksheet in a Notes document as an OLE object, so it can be dynamically updated whenever the originating worksheet is modified.<:f>

@Bullet@<+@><:s><:#200,8486>Requires file locking

@Bullet@<+@><:s><:#400,8486>Notes can track and save multiple versions of documents, but several people in different locations can edit the same document simultaneously.

@Bullet@<+@><:s><:#200,8486>Involves manipulation and reporting of large amounts of data

@Chead title@<:s><:R1,1,1,1080,><:#200,8486>Ways to develop Notes with other Lotus products

<:R1,1,1,1080,><:#200,8486>NEED INFORMATION FROM REVIEWERS++

<:R1,1,1,1080,><:#200,8486>The following Lotus products have built-in connections to the Notes software.

<:R1,1,1,1080,><:#800,8486> In addition, third-party products offer highly-specialized applications, such as executive information, data access, and multimedia systems, and products for government and healthcare agencies. Ask your Lotus representative or reseller for the latest editi
on of <+">The Lotus Notes Guide<-"> to learn about the wide range of Lotus and third-party products and services that are available.

@Dhead@<:R><:#200,8486>Lotus SmartSuite products

@Bullet@<:s><:#200,8486>1-2-3

@Bullet@<:s><:#200,8486>Word Pro

@Bullet@<:s><:#200,8486>Approach

@Bullet@<:s><:#200,8486>Freelance Graphics

@Bullet@<:s><:#200,8486>Lotus Forms

@Bullet@<:s><:#200,8486>Organizer

@Dhead@<:s><:#200,8486>Phone Notes

<+@><:s><:#200,8486><:X8,8;Index "Extending Notes with other products" # "Phone Notes"><:X8,8;Index "Notes" # "and Phone Notes"><:X8,8;Index "Phone Notes" # "and Notes">to come

@Dhead@<:s><:#200,8486>Video Notes

<+@><:s><:#200,8486><:X8,8;Index "Extending Notes with other products" # "Video Notes"><:X8,8;Index "Notes" # "and Video Notes"><:X8,8;Index "Video Notes" # "and Notes">to come

@Dhead@<:s><:#200,8486>Lotus Notes Document Imaging 

<+@><:s><:#200,8486><:X8,8;Index "Extending Notes with other products" # "Lotus Notes Document Imaging"><:X8,8;Index "Notes" # "and Lotus Notes Document Imaging"><:X8,8;Index "Lotus Notes Document Imaging" # "and Notes">to come

@Dhead@<:R1,1,1,1080,><:#200,8486>Others??++

<+@><:s><:R1,1,1,1080,><:#200,8486>Lotus Sound, Lotus Multimedia Manager?

@Bhead title@<:s><:R1,2,1,360,1,720,><:#220,8486>About the structure of an application

<+@><:s><:I0,0,0,0><:S+-1><:R1,2,1,120,1,720,><:#422,8486><:f,,>Every Notes application includes at least one database; each 
<:f><:f,,>Notes database incorporates <:f><:f,,>three basic components: forms, fields, and views.

<+@><:s><:I0,0,0,0><:S+-1><:R1,2,1,120,1,720,><:#422,8486><:f,,>In addition, agents (Notes<:f><:f,,> macros<:f><:f,,>), actions, formulas, and scripts play an important role in giving an application sophisticated automation and processing power. 
<:f>

@Chead@<:s><:R><:#200,8486><:f,,>D<:f><:f,,>atabases

<:#800,8486><:X8,8;Index "Database" # "defined in Notes"><:X8,8;Index "Database" "" ", See also Application"><:f><:f,,>A<:f> database<:f,,> is a collection of related information 
<:f><:f,,>stored in a single file. <:f><:f,,>The database can be as small as a workgroup</R><:f><:f,,>s phone book that contains a few documents<:f><:f,,>, or as large as the complete personnel records for 5,000 employees (<:f><:f,,>as much as 1 gigabyte of
 information++)<:f><:f,,>. Every Notes application uses at least one database; some applications use more than one database.

<:s><:#200,8486><:f,,>Databases are represented on each user</R><:f><:f,,>s workspace by icons.

<:s><:#200,8486>{bmc filename.bmp}

@Chead title@<:s><:#200,8486><:f,,>Forms

<:s><:#400,8486><:X8,8;Index "Form" #><:X8,8;Index "Database" # "form"><:X8,8;Index "Document" #><:X8,8;Index "Database" # "document">A form determines the framework for the information to be stored in the database. When you design a form, you decide what components to pla
ce on the form and how they should look to users. 

<:s><:#200,8486>{bmc filename.bmp}

<:s><:#800,8486>A form can contain fields to display data and text, colorful graphics to make the form attractive and easy-to-use, and special objects that can link to other products' data. Most databases have several forms, each serving a particular purpose. For example, 
a discussion database usually includes a form to begin a new topic of discussion and another form to respond to topics.

@Dhead@<:s><:#200,8486>Documents

<:s><:#800,8486><:f,,>Each database record is called a <:f><:f,,>document. <:f> Documents store the information within a database. To compose a document, a user chooses a form from the Create menu, fills out  the form, and saves it as a document in the database. If you</R>
re familiar with other database products, think of Notes forms as the screen layout for an application and documents as the records in an application.

<:s><:#200,8486>{bmc filename.bmp}

@Chead title@<:s><:#200,8486>Fields

<:s><:#800,8486><:X8,9;Index "Field" #><:X8,9;Index "Database" # "field">A field is an area on a form that contains a single type of information</W>text, rich text (including a variety of type styles, graphics, and multimedia objects), numbers, times or dates, and user nam
es. The fields on a form define the kind of information each document contains. You can also group related fields into access-controlled sections 
<:X8,9;Index "Sections" # "about access-controlled sections"><:X8,9;Index "Sections" #"about">that 
<:X8,9;Index "About" # "access-controlled sections">allow only certain people to edit the fields in the section.

<:s><:#200,8486>{bmc filename.bmp}

@Chead title@<:s><:#200,8486>Views

<:s><:#600,8486><:X8,9;Index "View" #><:X8,9;Index "Database" # "view">A view displays document summaries in rows and columns so users can find the documents they want to read. A view can include data extracted from document fields, calculation results, or totals and avera
ges across documents.

<:s><:#800,8486>Most databases have several views that organize and present the documents in different ways. For example, a discussion database may have three views: one that arranges documents in alphabetical order by their authors, a second view that shows documents by t
heir creation date, and a third view that sorts them by category name.

<+@><:s><:I0,0,0,0><:S+-1><:#633,8486>An approval application might have an "In Basket" view that categorizes documents by the next approver, a "Due Date" view that categorizes documents by the due date of the next action, and a "Request By" view that categorizes documents by who initiated the 
request. 

<+@><:s><:I0,0,0,0><:S+-1><:#422,8486>To read documents in a database, a user opens a view, then opens the document shown in an individual row.

<:s><:#200,8486>{bmc filename.bmp}

<:s><:#400,8486>A navigator may be added to a database to help users find views or documents without using menu commands.

<:s><:#200,8486>{bmc filename.bmp}

@Chead title@<:s><:#200,8486>Formulas and scripts

<:s><:#800,8486><:X8,9;Index "Database" # "formula"><:X8,9;Index "Database" # "LotusScript program"><:X8,9;Index "LotusScript" #><:X8,9;Index "Formula" #>Underlying Notes applications are formulas or LotusScript programs that can define the contents of documents and views,
 determine how data is displayed, and perform complex workflow and automation tasks. You can build into an application's design Notes @functions or programs based on the LotusScript class libraries that ship with Notes. 

@See also prnt@<:s><:#400,8486>For more information about using LotusScript and @functions in Notes applications, see "Where to use scripts and formulas" in Chapter 1 of the 
<+">Programmer's Guide<-">.

@Chead title@<:s><:#200,8486>Agents and actions

<:s><:#200,8486>ADD EVENTS TO THIS LIST??

<:s><:#400,8486><:X8,9;Index "Database" # "action"><:X8,9;Index "Database" # "agent"><:X8,9;Index "Agent" #><:X8,9;Index "Action" #><:X8,9;Index "Database" # "automation"><:X8,9;Index "Automation" #>Database agents, form actions, and view actions are all design features th
at can add automation to any application.

<+@><:s><:I0,0,0,0><:S+-1><:#844,8486>For example, a workflow agent could check a database every day for stalled approvals and send reminders or reroute the workflow. A tracking agent could check for low inventory or other problems and notify the appropriate person. A maintenance agent can dele
te or archive old documents or change the contents of a field in documents that meet certain conditions.

<+@><:s><:I0,0,0,0><:S+-1><:#844,8486>Form and view actions are portrayed as buttons or menu commands. Simple actions can make it easy for novice users to perform Notes menu commands, such as preparing a document for editing or saving a document. Sophisticated actions that are built around form
ulas or LotusScript programs can do more complex work that can't be accomplished through Notes menu commands, SUCH AS ??? ++.

@See also prnt@<+@><:s><:I0,0,0,0><:S+-1><:#427,8486>For more information about writing a LotusScript program for agents, see  "Writing scripts and formulas for agents" and "Writing scripts and formulas for actions" in Chapter 1 of the 
<+">Programmer's Guide<-">.

@See also hlp@<:s><:#110,8486>

@See also btn@<:s><:#200,8486>

@Crossref@<:#200,8486><+)>Where to use scripts and formulas<-)><+*>H_WHERE_TO_USE_SCRIPTS_AND_FORMULAS<-*>

@Crossref@<:#200,8486><+)>Writing scripts and formulas for agents<-)><+*>H_WRITING_SCRIPTS_AND_FORMULAS_FOR_AGENTS<-*>

@Crossref@<:#200,8486><+)>Writing scripts and formulas for actions<-)><+*>H_WRITING_SCRIPTS_AND_FORMULAS_FOR_ACTIONS<-*>

@Crossref@<:#400,8486><+)>Ways to explore existing database designs<-)><+*>H_WAYS_TO_EXPLORE_EXISTING_DATABASE_DESIGNS<-*>

@Crossref@<:#200,8486><+*><+)>About Notes applications<-)><-*><+*>H_ABOUT_NOTES_APPLICATIONS<-*>

@Bhead title@<:s><:R1,2,3,240,1,399,><:#220,8486><-)>About Notes database security<-!>

<:s><:R><:#600,8486><:X8,10;Index "About" # "security"><:X8,10;Index "Design" # "building security into the">Security should be considered during all phases of database planning, development, and rollout. Server administrators, application developers, and database managers sha
re the responsibility for database security. 

<:s><:#400,8486><:f,,>E<:f><:f,,>ach level of Notes security restricts information to an ever</m>smaller group of users and 
<:f><:f,,>cannot override a higher<:f><:f,,> level. <:f>

<:s><:#200,8486><+!>Server</m>level security<-!>

<:s><:#600,8486><:X8,10;Index "Security" # "server level"><:X8,10;Index "Server" # "security"><:f,,>Before users can work on databases stored on a Notes server, they must gain access to the server itself. Server access is determined by the certificates attached to the 
<:f><:f,,>User ID file and <:f><:f,,>by <:f><:f,,>the server administrator.<:f>

@See also prnt@<:s><:#200,8486>For more information about server-level security, see the Administrator's Guide.

<:s><:#200,8486><+!>Database</m>level security<-!>

<:s><:#800,8486><:f,,>Every shared database <:f><:f,,>has an access control list (ACL) that determines<:f><:f,,> who can open 
<:f><:f,,>the <:f><:f,,>database <:f><:f,,>and what kinds of changes each user can make<:f><:f,,>. Access levels range from database Manager (complete control over the database) to No Access. 
<:f>The database manager sets database</m>level security in the Database Access Control List dialog box.

<:s><:#600,8486>Information in databases can also be protected from direct access outside of Notes (for instance, copying a server-based database at the operating system level) by selecting the Local security option that encrypts the database and allows only certain people
 to decrypt it.

@See also prnt@<:s><:#200,8486>For more information about database-level security, see the Database Manager's Guide.

<:s><:#200,8486><+!>Document</m>level security<-!>

<:s><:#800,8486><:f,,>A document can <:f><:f,,>restrict <:f><:f,,>who can <:f><:f,,>read its contents, even if they have Reader access to the database<:f><:f,,>. 
<:f><:f,,>A document inherits from its original form the form's <:f><:f,,>Read ACL 
<:f><:f,,>and the readers listed in the <:f><:f,,>Reader Names field<:f><:f,,>. 
<:f>An author or editor can also restrict readers of an individual document by changing the Read ACL in the Document Properties InfoBox. 

<:s><:#400,8486>WHAT ABOUT EDITING SECURITY - Add??? Author names field? "Must have at least Editor access to change"

<:s><:#600,8486>Adding security features to forms is faster and more flexible if the names in the database ACL are already organized into groups--either by using group names from the public Name & Address Book or by creating access roles.

@See also prnt@<:s><:#400,8486>For more information, see "Restricting who can read documents" in Chapter 3 and "Making a field that lists readers" in Chapter 4.

<:s><:#200,8486><+!>Field</m>level security<-!>

<:s><:#1000,8486><:X8,11;Index "Fields" # "security"><:X8,11;Index "Security" # "field level"><:f,,>A designer or author can restrict<:f><:f,,> 
<:f><:f,,>reading part of a document<:f><:f,,> by making a field encryptable. 
<:f><:f,,>Only users with the correct encryption key can decrypt the field to view its contents. 
<:f><:f,,>Once encryption keys are associated with a document, all encryptable fields within the document are encrypted, and can only be decrypted using one of the associated keys. Only the fields that are encryptable are hidden from users without the key; 
the remaining fields are still visible.

<:s><:#400,8486><:f,,>A designer can prevent authors from editing part of their own documents by 
<:f>choosing the field security option, "Must have at least Editor access to use."

@See also prnt@<:s><:#200,8486>For more information about security for sections and fields, see Chapter 4.

@See also hlp@<:s><:#110,8486>

@See also btn@<:s><:#200,8486>

@Crossref@<:#200,8486><:f,,>Server security?? Admin Help++<:f>

@Crossref@<:#200,8486><+)>About the Access Control List<-)><+*>H_ABOUT_THE_ACCESS_CONTROL_LIST<-*>

@Crossref@<:#200,8486><+)>Restricting who can read documents<-)><+*>H_RESTRICTING_WHO_CAN_READ_DOCUMENTS<-*>

@Crossref@<:#200,8486><+*><+)>Making a field that lists readers<-)><-*><+*>H_MAKING_A_FIELD_THAT_LISTS_READERS<-*>

@Crossref@<:#400,8486><+)>Making a field that an author can't change<-)><+*>H_MAKING_A_FIELD_THAT_AN_AUTHOR_CAN'T_CHANGE<-*>

@Crossref@<:#200,8486><+)>About making a field that encrypts data<-)><+*>H_ABOUT_MAKING_A_FIELD_THAT_ENCRYPTS_DATA<-*>

@See also btn@<:s><:#200,8486><-)><+*>

@See also btn@<:#200,8486><+)>{bmc 1details.bmp}See examples<-)><+*>H_EXAMPLES:_ABOUT_NOTES_DATABASE_SECURITY<-*>

@Chead title@<:s><:#200,8486>Examples: About Notes database security

<:s><:#1200,8486><:X8,11;Index "Security" # "scenario"><:f,,><:X8,11;Index "Example" # "security scenario">No single security implementation is right for all sites, or for all databases at all times. Workgroup organization and size, along with server topology and company po
licy are all factors that must be considered when implementing a comprehensive security policy within a Notes system. Database managers and server administrators are the main protectors of<:f><:f,,> a database, but developers need to understand the features
 that can be built into a database's design to make individual pieces of information secure.<:f>

<+@><:s><:I0,0,0,0><:S+-1><:#221,8486><:><+!>Centralized Employee Information Database

<+@><:s><:I0,0,0,0><:S+-1><:#844,8486>Acme Industries is headquartered in San Francisco and has three sales offices. The Human Resources (HR) group manages a centralized database that contains information for each employee, including salary, performance, and benefits information. The database i
s replicated to the three sales offices, so that hiring managers at those sites can read and contribute to the database.

@1st lev para@<+@><:s><:I0,0,0,0><:S+-1><:#211,8486><:>The database stores a main document and three types of response documents for each employee:

@Bullet@<:s><:#400,8486>Employee Statistics - main document containing an employee's name, address, social security number, employee number, current job title, job grade, and current salary.

@Bullet@<:s><:#400,8486>Salary History - response document containing only the date of each raise and the employee's annual salary as a result of the raise.

@Bullet@<:s><:#400,8486>Performance Review - one or more response documents containing the employee's annual performance reviews. 

@Bullet@<:s>Benefits - response document summarizing the employee's current insurance, profit sharing, retirement, and education reimbursement options<-!><-!>

<+@><:s><:I0,0,0,0><:S+-1><:#221,8486><+!>Who uses this database?<-!>

<+@><:s><:I0,0,0,0><:S+-1><:#211,8486>There are three types of employees who use this database:

@Bullet@<:s><:#200,8486>Human Resources group

@1st lev para@<:s><:#600,8486>Four members of HR manage the database. Brynne Styles is director of Human Resources, Didier Thibault is her administrative assistant. Will Barber manages the Benefits Department. Suellyn Hayes chairs the compensation committee. 

@Bullet@<:s><:#200,8486>Department heads, supervisors, and administrative assistants

@1st lev para@<:s><:#800,8486>Supervisors and their administrative assistants contribute most of the basic data to the database; department heads can add or delete documents if needed<:>. Managers in the field hire autonomously; HR needs field offices to contribute information on employ
ees, so HR can assign compensation and benefits accurately.

@Bullet@<:s><:#200,8486>Payroll

@1st lev para@<:s><:#400,8486>The Payroll group needs to check employees' current salaries and benefits, but does not need to add documents.

<:s><:#200,8486><:><+!>Who can access the database?<-!>

<:s><:#1200,8486>Because the information in this database is confidential, access to the database itself is restricted. Brynne Styles manages the database, and as a backup has  Will Barber and two additional people from the Benefits department listed as managers in the ACL.
 Department heads have Editor access and can delete documents. Field supervisors have Author access and can delete documents. Field administrative assistants have Author access, but cannot delete documents. The Payroll department has Reader access. The defa
ult access is No access.

<:s><:#400,8486>The developer of the database no longer has Designer access. A manager gives the developer access on an as-needed basis on those rare occasions when redesign is needed.<:>

<+@><:s><:I0,0,0,0><:S+-2><:#331,8486><+!>What security features are built in to the design?<-!>

@1st lev para@<:s><:I0,0,0,0><:S+-1><:#221,8486><+!>Encrypted fields<-!>

@1st lev para@<:s><:I0,0,0,0><:S+-1><:#844,8486>Brynne Styles wants current salary and salary history to be hidden from administrative assistants. She creates an encryption key and has the developer of the database assign the encryption key to the AnnualSalary field on the Salary History form and the Cur
rentSalary field on the Employee Statistics form. 

<:s><:#1000,8486>When Styles sends the key to Will Barber, she replies Yes to the "Should recipients be allowed to send this key to others?" question. But when Styles sends the key to Thibault and Hayes in HR, department heads and supervisors, and Payroll, she answers No so
 they cannot send the key to others. This enables Barber to distribute the key to others if needed, but allows Barber and Styles to maintain an accurate list of key holders. 

@1st lev para@<:s><:I0,0,0,0><:S+-1><:#633,8486>When administrative assistants edit or read the Employee Statistics and Salary History documents for an employee, they cannot see the information in the AnnualSalary or CurrentSalary fields because they don't have the encryption key.

@1st lev para@<:s><:I0,0,0,0><:S+-1><:#221,8486><+!>Limited editor access to a field<-!>

<+@><:s><:I0,0,0,0><:S+-1><:#633,8486>The CurrentSalary field is assigned the security property "Must have at least Editor access." Supervisors can write salary history documents, and have access to the CurrentSalary field because they have the encryption key, but they cannot change the entry i
n the CurrentSalary field.<:>

<+@><:s><:I0,0,0,0><:S+-1><:#221,8486><+!>Limited document readers<-!>

<+@><:s><:I0,0,0,0><:S+-1><:#844,8486>To prevent the Payroll department from seeing performance reviews, the Performance Review form has a Read ACL associated with it. Every group except Payroll is included in the Read ACL. HR, department heads, supervisors, and administrative assistants can re
ad any documents created with the Performance Review form, but the Payroll members cannot.

@Chead title@<:s><:#200,8486>About features that aren't security features

<:s><:#400,8486><:f,,>Several design features allow you to <:f><:f,,>protect data or designs from accidental changes. Do not use these features 
<:f><:f,,>as true security mechanisms that <:f><:f,,>protect data.

<:s><:#200,8486><+!>Hidden design

<:#200,8486>Include?? DOESN'T PROTECT DATA, BUT DOES PROTECT DESIGN CHANGES, RIGHT??++

<:s><:#200,8486><+!>Hidden views<-!>

<:s><:#800,8486><:X8,13;Index "Non-secure features" # "hidden views"><:X8,13;Index "Views" # "hidden views, not a security feature">As with forms, you can hide a view by enclosing the leftmost name in parentheses, thus removing it from the View menu. A user with Designer o
r Manager access can remove the pa<:f,,>rentheses from the view name to unhide it. Users with Editor, Author, or Reader 
<:f><:f,,>access can make a copy of the database and unhide the view.

<:s><:#200,8486><+!>Read ACLs for views<-!>

<:s><:#600,8486>You can restrict access to documents in a view by defining a Read ACL for the view; however this doesn</R>t prevent users from creating their own private views to display the information in the restricted view. 

<:s><:#200,8486><+!>Edit <-!><+!>ACLs for views<-!>

<:s><:#600,8486>You can restrict editing of documents in a view by defining an Edit ACL for the view; however this doesn</R>t prevent users from creating their own private views to display and edit the information in the restricted view. TRUE ?? ++

<:s><:#200,8486><+!>Hidden forms<-!>

<:s><:#400,8486><:X8,13;Index "Non-secure features" # "hidden forms"><:X8,13;Index "Forms" # "hidden forms, not a security feature">You can hide a form by enclosing its leftmost name in parentheses, as in (Performance Review)|Review or by deselecting "Include in Create Men
u" in the Form Properties InfoBox. 

<:s><:#400,8486>A user with Designer or Manager access can remove the parentheses from the form name or selecting "Include in Create Menu."

<:s><:#200,8486><+!>Sections<-!>

<:#200,8486>IS THIS REALLY TRUE - SECTIONS SEEM SECURE??++

<:s><:R1,2,1,360,1,720,><:#800,8486>Access-controlled sections allow you to define special areas on a form and authorize only specific people to edit fields in that area. A section contains fields and static text, just like the rest of the form. An access-controlled section doesn</R>t physica
lly protect data because a user can potentially modify the section through a different form that doesn</R>t contain sections. To make a section truly secure, you must

<:s><:R><:#200,8486><+!>Hidden fields<-!>

<:s><:#600,8486><:X8,13;Index "Non-secure features" # "hidden fields"><:X8,13;Index "Fields" # "hidden fields, not a security feature">When designing a form, you can 
</S>hide</T> a field by selecting it and using the "Hide when" <:f,,>options in the Text Paragraph dialog box. When a document is created with the form, the selected field is hidden when the document is in any of these states: reading, copying, editing, or 
printing.

<:s><:#600,8486>Any user with access to the Notes server where the database is stored can copy the database to his or her workstation at the operating system level, and use the implicit Manager access to examine the contents of those hidden fields with File - Document Prop
erties.

<:s><:#200,8486><+!>Names fields<-!>

<:#800,8486>The <:X8,13;Index "Non-secure features" # "names fields"><:X8,13;Index "Names" # "names fields, not a security feature"><:X8,13;Index "Fields" # "names fields, not a security feature">Names field type is a mechanism for displaying distinguished user names i
n different formats, but it is not capable of protecting data. To control access to a document, use Reader Names or Author Names fields instead. HOW DO AUTHOR NAMES PROTECT ACCESS?? SHOULDN"T THIS SAY "MUST HAVE AT LEAST EDITOR ACCESS TO USE??

<:s><:R1,2,1,360,1,720,><:#200,8486><+!>Access roles<-!>

<:s><:R><:#1000,8486>Users with physical access to the Notes server where the database is stored can copy the database at the operating system level. Since a local database always allows users implicit Manager access (unless "Local security" is chosen as a database property), t
hey could change the ACL to view information protected by access roles. Physical access to Notes servers must be carefully guarded if the database isn't encrypted locally.

@Ahead@<:s><:R1,2,1,360,1,720,><:#240,8486>Ways to start learning about development

@Bullet@<:R1,2,1,360,1,720,><:#200,8486><-#><+)>Installing Notes files<-)><+*>H_INSTALLING_NOTES_FILES<-*><-#><-#><-#>

@Bullet@<:R1,2,1,360,1,720,><:#200,8486><+)>Setting up sample databases<-)><+*>H_SETTING_UP_SAMPLE_DATABASES<-*> 

@Bullet@<:R1,2,1,360,1,720,><:#200,8486><+)>Setting up development shortcuts<-)><+*>H_SETTING_UP_DEVELOPMENT_SHORTCUTS<-*> 

@Bullet@<:R1,2,1,360,1,720,><:#400,8486><+)>Getting acquainted with Notes design tools<-)><+*>H_GETTING_ACQUAINTED_WITH_NOTES_DESIGN_TOOLS<-*> 

@Bullet@<:R1,2,1,360,1,720,><:#200,8486><+)>Exploring existing database designs<-)><+*>H_WAYS_TO_EXPLORE_EXISTING_DATABASE_DESIGNS<-*> 

@Bullet@<:R1,2,1,360,1,720,><:#200,8486><+)>Experimenting with existing databases<-)><+*>H_EXPERIMENTING_WITH_EXISTING_DATABASES<-*> 

@Bhead title@<:s><:R1,2,1,360,1,720,><:#220,8486>Installing Notes files

<+@><:s><:I0,0,0,0><:S+-1><:R1,2,1,360,1,720,><:#211,8486><:X8,14;Index "Getting started" # "installing files"><:X8,14;Index "Installing files" #>To develop Notes applications, you should install, or have access to, the following Notes files:

@Bullet@<:s><:R1,2,1,360,1,720,><:#200,8486>Template files

@Bullet@<:s><:R1,2,1,360,1,720,><:#200,8486>Example files

@Bullet@<:s><:R1,2,1,360,1,720,><:#200,8486>Notes Help

<:s><:R1,2,1,360,1,720,><:#400,8486>It's more convenient, if you have enough disk space, to install all the files on your local workstation; however, template and example files and Notes Help are usually available on servers. 

@Bhead title@<+@><:s><:I0,0,0,0><:S+-1><:R1,2,1,360,1,720,><:#240,8486>Setting up sample databases

<+@><:s><:I0,0,0,0><:S+-1><:R1,2,1,360,1,720,><:#211,8486><:X8,14;Index "Database" # "setting up samples"><:X8,14;Index "Sample databases" # "setting up"><:X8,14;Index "Example databases" # "setting up"><:X8,14;Index "Templates" # "setting up"><:X8,14;Index "Getting started" # "setting up samples and templates">Be
fore you can examine templates and examples, you must add them to your workspace.

@Numbered list@<:s><:R1,2,1,360,1,720,><:#200,8486>From the Notes workspace, choose File - Database - Add Workspace Icon.

@Numbered list@<:s><:R1,2,1,360,1,720,><:#200,8486>Leave Local selected in the Server list box if you installed templates and examples on your hard disk.

@Numbered list@<:s><:R1,2,1,360,1,720,><:#400,8486>If the templates are on a server, select a server name from the list and click Open or click List All and highlight and click Open for another server.

@Numbered list@<:s><:R1,2,1,360,1,720,><:#200,8486>In the filename box, type the file name for the template you want (for example, DISCUSS.NTF).

@1st lev para@<:s><:R1,2,1,360,1,720,><:#200,8486>(Since templates have an .NTF extension, they don't appear in the regular list of databases.)<:X8,14;Index "NTF" #><:X8,14;Index "Templates" # "NTF file extension"><:X8,14;Index "Database" # "NTF file extension"><:X8,14;Index "Filename" # "NTF file extension">

@See also prnt@<:s><:R1,2,1,360,1,720,><:#400,8486>For a list of template file names, see "Application templates" and "Notes example databases" in Appendix A.

@Numbered list@<:s><:R1,2,1,360,1,720,><:#200,8486>Click Add Icon.

@Numbered list@<:s><:R1,2,1,360,1,720,><:#200,8486>Repeat Steps 4 and 5 to add each template you want on your workspace.

@Numbered list@<:s><:R1,2,1,360,1,720,><:#200,8486>Select the Examples subdirectory in the Database list and click Open.

@Numbered list@<:s><:R1,2,1,360,1,720,><:#200,8486>Select the example you want (for example, Contract Library).

@Numbered list@<:s><:R1,2,1,360,1,720,><:#200,8486>Click Add Icon.

@Numbered list@<:s><:R1,2,1,360,1,720,><:#200,8486>Repeat Steps 8 and 9 to add each example you want on your workspace.

@Numbered list@<:s><:R1,2,1,360,1,720,><:#200,8486>Click Done.

@See also hlp@<:s><:R1,2,1,360,1,720,><:#110,8486>

@See also btn@<:s><:R1,2,1,360,1,720,><:#200,8486>

@Crossref@<:R1,2,1,360,1,720,><:#200,8486><+)>Application templates<-)><+*>H_APPLICATION_TEMPLATES<-*>

@Crossref@<:R1,2,1,360,1,720,><:#200,8486><+)>Notes example databases<-)><+*>H_NOTES_EXAMPLE_DATABASES<-*>

@Bhead title@<+@><:s><:I0,0,0,0><:S+-1><:R1,2,1,360,1,720,><:#240,8486>Setting up development shortcuts

<+@><:s><:I0,0,0,0><:S+-1><:R1,2,1,360,1,720,><:#422,8486><:X8,15;Index "Development" # "setting up shortcuts"><:X8,15;Index "SmartIcons" # "setting up designer SmartIcons"><:X8,15;Index "Getting started" # "setting up designer SmartIcons"><:X8,15;Index "Design" # "SmartIcons set"><:X8,15;Index "Shortcuts" # "designer SmartIcons set">
<:f><:f,,>The Designer SmartIcons set offers one-click shortcuts for design commands that you would normally choose from the menu. 
<:f>

@Numbered list@<:s><:R1,2,1,360,1,720,><:#200,8486>From the Notes workspace, choose File - Tools - SmartIcons Setup.

@Numbered list@<:s><:R1,2,1,360,1,720,><:#200,8486>Select the Design SmartIcons set.

@Numbered list@<:s><:R1,2,1,360,1,720,><:#200,8486>Click OK.

@Numbered list@<:s><:R1,2,1,360,1,720,><:#200,8486>The Designer SmartIcons are now your default palette.

@1st lev para@<:s><:R1,2,1,360,1,720,><:#200,8486>{bmc filename.bmp}

@1st lev para@<:s><:R1,2,1,360,1,720,><:#200,8486>Click and hold the right mouse button over each picture to see what each icon does.

@Bhead title@<+@><:s><:I0,0,0,0><:S+-1><:R1,2,1,360,1,720,><:#240,8486>Getting acquainted with Notes design tools

<+@><:s><:I0,0,0,0><:S+-1><:R1,2,1,360,1,720,><:#422,8486><:X8,15;Index "Design" # "tools"><:X8,15;Index "Design mode" #><:X8,15;Index "Getting started" # "learning about design tools"><:X8,15;Index "Development" # "switching to design mode"><:X8,15;Index "Database" # "designing"><:X8,15;Index "Tools" # "for designing databases">
Any changes or additions you make to a database design are made by using the Notes design tools. You access the design tools by either:

@Bullet@<:s><:R1,2,1,360,1,720,><:#200,8486>Selecting a database icon on your workspace and choosing View - Design

@Bullet@<:R1,2,1,360,1,720,><:#200,8486>Double-clicking a database and clicking the green arrow (twistie) next to the Design tool

<:s><:R1,2,1,360,1,720,><:#400,8486>When the Design tools are displayed, click the type of component (such as Forms) that you want to design.

<:s><:R1,2,1,360,1,720,><:#200,8486>{bmc filename.bmp}

@Chead title@<+@><:s><:I0,0,0,0><:S+-1><:R1,2,1,360,1,720,><:#221,8486>Creating a starter database

<+@><:s><:I0,0,0,0><:S+-1><:R1,2,1,360,1,720,><:#211,8486>After you create a new discussion database, you can use the Notes design tools with it. 

<+@><:I0,0,0,0><:S+-1><:R1,2,1,360,1,720,><:#211,8486>INCLUDE MAC INSTRUCTIONS??++

@Numbered list@<:s><:R1,2,1,360,1,720,><:#200,8486>From the Notes workspace, choose File - Database - New.

@Numbered list@<:s><:R1,2,1,360,1,720,><:#200,8486>Leave Server: Local selected.

@Numbered list@<:s><:R1,2,1,360,1,720,><:#200,8486>Enter "My Discussion" as the title.

@Numbered list@<:s><:R1,2,1,360,1,720,><:#200,8486>Press TAB to fill in the Filename edit box.

@Numbered list@<:s><:R1,2,1,360,1,720,><:#400,8486>Select Discussion as the template. (If you want to see templates stored on a server, select "Template Server" and select a server from the list.)

@Numbered list@<:s><:R1,2,1,360,1,720,><:#200,8486>Click About to view a short description of the template.

@Numbered list@<:s><:R1,2,1,360,1,720,><:#200,8486>Deselect "Inherit future design changes." 

@Numbered list@<:s><:R1,2,1,360,1,720,><:#200,8486>Click OK.

@1st lev para@<:s><:R1,2,1,360,1,720,><:#400,8486>Notes creates the database, adds its icon to your workspace, and opens the database to show you the introductory "About Discussion" document.

@Numbered list@<:s><:R1,2,1,360,1,720,><:#200,8486>Press ESC twice.

@Chead title@<:s><:R1,2,1,360,1,720,><:#200,8486>Looking at the Design tools

@Numbered list@<:s><:R1,2,1,360,1,720,><:#200,8486>Select a database icon and choose View - Design.

@1st lev para@<:s><:R1,2,1,360,1,720,><:#400,8486><:f,,>The left pane is the Navigator pane, from which you can select items to help you do your work. 
<:f><:f,,>The right pane is the View Pane, whose contents change depending on what you're working on. 
<:f>

@1st lev para@<:s><:R1,2,1,360,1,720,><:#200,8486>{bmc filename.bmp}

@Numbered list@<:s><:R1,2,1,360,1,720,><:#200,8486>Click a design tool name to display the design elements for the database in the View pane.

@1st lev para@<:s><:R1,2,1,360,1,720,><:#200,8486>{bmc filename.bmp}

@Numbered list@<:s><:R1,2,1,360,1,720,><:#200,8486>To look more closely at a design element, highlight it in the View Pane and double-click.

@1st lev para@<:s><:R1,2,1,360,1,720,><:#600,8486><:X8,16;Index "Design" # "opening form for"><:X8,16;Index "Design" # "opening view for"><:X8,16;Index "Form" # "open in design mode"><:X8,16;Index "View" # "open in design mode">The builder window opens for that element and the Notes menu changes to be appr
opriate to the task you're doing. You are now in "design mode" in that form, field, or view. The builder windows for forms and views are shown below.

@1st lev para@<:s><:R1,2,1,360,1,720,><:#200,8486>{bmc filename.bmp}

@1st lev para@<:s><:R1,2,1,360,1,720,><:#200,8486>{bmc filename.bmp}

@See also prnt@<:s><:R1,2,1,360,1,720,><:#200,8486>For information about designing forms, fields, and views, see Chapters 3, 4, and 5 for information.

@Numbered list@<:s><:R1,2,1,360,1,720,><:#600,8486><:X8,16;Index "Properties" # "maneuvering in info box"><:f><:f,,><:X8,16;Index "Info box" # "maneuvering in">C<:f><:f,,>hoose the Form or View Properties 
<:f><:f,,>from the menu bar to open the Properties InfoBox for a form or view. (To see properties for fields on a form, double-click the rectangle that surrounds the field definition and choose Field - Field Properties.) 
<:f>

@1st lev para@<:s><:R1,2,1,360,1,720,><:#200,8486>{bmc filename.bmp}

@Numbered list@<:s><:R1,2,1,360,1,720,><:#200,8486><:X8,16;Index "Info box" # "collapsing"><:f,,>Click each tab to <:f><:f,,>see or change r<:f><:f,,>elated sets of options.<:f>

@1st lev para@<:s><:R1,2,1,360,1,720,><:#200,8486>Changing a setting in the InfoBox automatically makes the change in the form, view, or field.

@Numbered list@<:s><:R1,2,1,360,1,720,><:#400,8486>Double-click the title bar to collapse the InfoBox; double-clicking the title bar again expands it. As you work on different design elements, the InfoBox changes to be appropriate for that design element.

@1st lev para@<:s><:R1,2,1,360,1,720,><:#200,8486>{bmc filename.bmp}

@Numbered list@<:s><:R1,2,1,360,1,720,><:#200,8486>Double-click the control button in the top left corner to close the InfoBox.

@1st lev para@<:s><:R1,2,1,360,1,720,><:#200,8486>{bmc filename.bmp} (show Close menu)

@Numbered list@<:s><:R1,2,1,360,1,720,><:#200,8486><:X8,16;Index "Design mode" # "leaving">Click on the form or view you're working on and press ESC to leave the builder window. 

@Numbered list@<:s><:R1,2,1,360,1,720,><:#200,8486>Click Yes to save any changes you've made or No to exit without saving.

@Numbered list@<:s><:R1,2,1,360,1,720,><:#200,8486><:X8,16;Index "Exiting" # "design mode">Press ESC to close the database.

@Bhead title@<+@><:s><:I0,0,0,0><:S+-1><:R1,2,1,360,1,720,><:#240,8486>Experimenting with existing databases

<:s><:S+-1><:R1,1,1,720,><:#422,8486><:X8,16;Index "Learning" # "by modifying existing databases"><:X8,16;Index "Getting started" # "by modifying existing databases">If you learn best by doing, make a copy of a database and try out your ideas. You can copy any database you're able to read, suc
h as the example databases or a database someone else created.

@Numbered list@<:s><:R><:#400,8486>Choose File - Database - Add Workspace Icon, selecting the database you want to copy, click Add Icon, and click Done.

@Numbered list@<:s><:#200,8486>Select the icon for the database you want to copy and choose File - Database - New Copy.

@Numbered list@<:s><:#200,8486>Leave Server: Local selected.

@Numbered list@<:s><:#200,8486>In the Title box, give your new database a name that distinguishes it from the existing database.

@1st lev para@<:#400,8486>UI NOTE -- THIS WAS NOT CHANGED IN 125 AS IT WAS FOR DATABASE - NEW. THEY SHOULD BE THE SAME.++

@Numbered list@<:s><:R1,2,1,360,1,720,><:#200,8486>Press TAB to fill in the Filename edit box.

@Numbered list@<:s><:R><:#400,8486>Select "Database design only" (deselect "Copy documents" on the Macintosh) if you only want to see the design.

@Numbered list@<:s><:#400,8486>Select "Database design and documents" (select "Copy documents" on the Macintosh) if you want to see the effect that design changes have on documents.

@Numbered list@<:s><:#200,8486>Deselect "Access Control List."

@Indnt note@<:s><:#200,8486>  Do not copy the Access Control List because it may not allow you to modify the database.

@Numbered list@<:s><:#200,8486><-!>Click OK (Copy on the Macintosh).

@Numbered list@<:s><:R1,2,3,240,1,399,><:#200,8486>Select the icon for the new copy and choose File - Database - Properties.

@Numbered list@<:s><:R1,2,3,240,1,399,><:#200,8486>Click the Design tab and make sure "Inherit design from template" is not selected.

@Numbered list@<:s><:R1,2,3,240,1,399,><:#200,8486>Double-click the control button in the top left corner to close the InfoBox.

@Numbered list@<:s><:R1,2,3,240,1,399,><:#200,8486>Choose View - Design.

@Numbered list@<:s><:R1,2,3,240,1,399,><:#200,8486>Click one of the design tools and double-click a design element.

@See also prnt@<+@><:s><:I0,0,0,0><:S+-1><:R1,2,1,360,1,720,><:#422,8486>Click Help in dialog boxes and info boxes for more information or browse Chapters 3, 4, and 5 for specifics about designing forms, fields, and views.

@Bhead title@<+@><:s><:I0,0,0,0><:S+-1><:R1,2,1,360,1,720,><:#240,8486>Ways to explore existing database designs

<+@><:s><:I0,0,0,0><:S+-1><:R1,2,1,360,1,720,><:#633,8486><:X8,17;Index "Getting started" # "exploring existing designs"><:X8,17;Index "Design" # "exploring existing designs"><:X8,17;Index "Learning" # "by exploring existing designs"><:X8,17;Index "Database" # "exploring existing designs">The templates and example
s, as well as other databases to which you have access, can help you learn about database design standards and provide you with ideas for your own applications. You can explore how a database is constructed by

@Bullet@<:R1,2,1,360,1,720,><:#200,8486><+)>Viewing a summary of a database's design<-)><+*>H_VIEWING_A_SUMMARY_OF_THE_DESIGN<-*> 

@1st lev para@<:s><:R1,2,1,360,1,720,><:#400,8486>Creating a design synopsis and reading the Help documents familiarize you with a database's overall design for learning, planning, or troubleshooting.<:f,,> 
<:f>

@Bullet@<:R1,2,1,360,1,720,><:#400,8486><+)>Examining individual forms, fields, views, and formulas<-)><+*>H_EXAMINING_INDIVIDUAL_DESIGN_ELEMENTS<-*> 

@1st lev para@<:s><:R1,2,1,360,1,720,><:#400,8486>Browse the design to analyze how another designer built a particular component or to see if a component is one you want to use.

@Chead title@<:s><:R1,2,1,360,1,720,><:#200,8486>Viewing a summary of the design

@Numbered list@<:s><:R1,2,1,360,1,720,><:#200,8486>Select the icon for the database whose design you want to know more about.

@Numbered list@<:s><:R1,2,1,360,1,720,><:#200,8486><:X8,17;Index "Synopsis" # "viewing design synopsis"><:X8,17;Index "Design" # "synopsis">Choose File - Database - Design Synopsis.

@Numbered list@<:s><:R><:#200,8486>Select the information you want to include in the synopsis.

@Numbered list@<:s><:#200,8486>Click OK.

@Numbered list@<:s><:#200,8486><:f,,>To print the summary, choose File - Print.

@Numbered list@<:s><:#200,8486><:f,,>To export the summary, choose File - Save as<:f><:f,,> - External File<:f>.

@Numbered list@<:s><:#400,8486>To paste the summary, choose Edit </m> Select All, Edit </m> Copy, in a Notes document or another product's file, choose Edit - Paste.

@Numbered list@<:s><:#200,8486>Press ESC to close the synopsis window.

@Numbered list@<:s><:R1,2,1,360,1,720,><:#200,8486>Choose Help - About <<database<;> to learn more about the purpose of the database or template.

@Numbered list@<:s><:R1,2,1,360,1,720,><:#200,8486>Choose Help - Using <<database<;> to read about how to use the forms and views.

@Numbered list@<:s><:R1,2,1,360,1,720,><:#200,8486>Choose File - Print to print any of the above summaries.

@Numbered list@<:s><:S+-1><:R1,1,1,720,><:#211,8486>Press ESC to close the Help documents.

@See also prnt@<:s><:R1,2,1,360,1,720,><:#400,8486>For a list of template file names, see "Application templates" and "Notes example databases" in Appendix A.

@See also hlp@<:s><:R1,3,1,360,1,720,1,1190,><:#110,8486>

@See also btn@<:s><:R1,3,1,360,1,720,1,1190,><:#200,8486>

@See also btn@<:R1,3,1,360,1,720,1,1190,><:#200,8486><+)>{bmc 1details.bmp}See details<-)><+*>H_DETAILS:_VIEWING_A_SUMMARY_OF_THE_DESIGN<-*>

@See also btn@<:s><:R1,3,1,360,1,720,1,1190,><:#200,8486>

@Crossref@<:R1,2,1,360,1,720,><:#200,8486><+)>Creating a design summary<-)><+*>H_CREATING_A_DESIGN_SUMMARY<-*>

@Dhead@<:s><:I0,0,0,0><:S+-1><:R1,2,1,360,1,720,><:#221,8486>Details: Viewing a summary of the design

<:s><:R><:#200,8486>UPDATE FOR BUILD 126++

<:s><:#200,8486>{bmc filename.bmp}

<:s><:#200,8486>Select Database to display the database title, location, categories, and so on.

<:s><:#200,8486>Select "Space Usage" to see the file size, number of documents, space used by the database, and so on.

<:s><:#200,8486>Select Replication to view the database's replication settings.

<:s><:#400,8486>Select "Access List" to see a name</m>by</m>name listing of the ACL, with the access level and access roles assigned to each.<:X8,18;Index "ACL" # "viewing summary information"><:X8,18;Index "Roles" # "viewing summary information"><:X8,18;Index "Access roles" # "viewing summary information">

<:s><:#200,8486>Select "Shared Field" to display the options chosen for each shared field in the database. 

<:s><:#200,8486>Select "Stored Query" to display ???++

<:s><:#400,8486>Select "Macro (Agent???)" to displ<:f,,>ay the options and formulas 
<:f><:f,,>chosen for each shared and private??? agent<:f><:f,,>. STILL CALLED MACRO IN BUILD 126 ++ 
<:f>

<:s><:#400,8486>Select "Forms" and select one or more forms to display the options chosen for each form and non-shared field on the form.

<:s><:#400,8486>Select "Views" and select one or more views to display the options chosen for each shared view and its columns.

@Chead title@<+@><:s><:I0,0,0,0><:S+-1><:R1,2,1,360,1,720,><:#221,8486>Examining individual design elements

<:s><:S+-1><:R1,1,1,720,><:#211,8486><:X8,18;Index "Design" # "viewing individual components"><:X8,18;Index "Getting started" # "viewing design elements"><:X8,18;Index "Learning" # "viewing design elements">To examine an individual design element and see its settings:

@Numbered list@<:s><:R1,2,1,360,1,720,><:#400,8486>Select the icon for the database whose design you want to know more about and choose View - Design.

@Numbered list@<:s><:S+-1><:R1,1,1,720,><:#422,8486>In the Design tools list in the Navigator pane, click the type of component you want to analyze (forms, subforms, shared fields, views, and so on).

@Numbered list@<:s><:S+-1><:R1,1,1,720,><:#211,8486>In the View Pane, double-click the component you want to know more about.

@Numbered list@<:s><:S+-1><:R1,1,1,720,><:#211,8486>If you get a warning about changing the design, click OK. (You won't be changing the design.)

@Numbered list@<:s><:S+-1><:R1,1,1,720,><:#211,8486>Choose Form, Field, or View - Properties to display the settings for the component.

@Numbered list@<:s><:S+-1><:R1,1,1,720,><:#211,8486>Click the tabs in the Properties InfoBox to review the settings.

@Numbered list@<:s><:S+-1><:R1,1,1,720,><:#211,8486>Choose File - Print to print a form.

@Numbered list@<:s><:R><:#200,8486>Close the InfoBox.

@Numbered list@<:s><:#200,8486>Click Design - Agents to see a list of agents.

@Numbered list@<:s><:#200,8486>Follow Steps 3 - 6 to see an agent's properties.

@Numbered list@<:s><:#200,8486>Press ESC to close the database.

<:R1,2,3,240,1,399,><:#200,8486>

>

[Embedded]
00093441
