Have a flat file with a few extra tables for look-ups. It prints leases 
and addenda for tenants. For the leases and many addenda, we do merge 
layouts of various lengths, from several dozen paragraphs, and various 
sub-paragraphs, to just a few paragraphs.

Challenge 1. Manage the paragraph numbering to allow insertions of new 
paragraphs and deletions, and automatic renumbering.

Challenge 2. Manage the paragraph and sub-paragraph numbers so that 
cross references (like, "as stated in Paragraph 9 above) will change 
when paragraphs are added and deleted.

I've begun to try a related table with arbitrarily large numbers (1000, 
2000, 3000, etc) to allow orderly insertions, but I don't get much 
beyond that. Been reading the many-to-many in Help, but haven't been 
able to come up with a working system.

Is there a plug-in or existing database that does this?

TIA. Simon
===============================

Hi Simon

Version?

In version 6 or earlier, you will need a many to many relationship: a master
file (tenant details), another master file (lease and addenda records from
which the lease agreements are composed) and a join file (lease and addenda
records for particular tenants).

Create a portal in the tenants file to the join file, sorted by paragraph
number.  Add the lease and addenda details to the join file portal by
selecting their unique serial number from a popup list referencing the lease
and addenda file (also reference another field which gives enough
information so facilitate selection).  Have all the other lease and addenda
fields lookup details from the lease and addenda file using the unique
serial number.

Make a field in the child file called paragraph number, set to autoenter
status portal row number.  When a new record is made in the join file via
the portal in the tenants file, this number will autoenter.

If you also need to reorder paragraphs, make the paragraph number that needs
to be changed smaller than the paragraph number it is to appear above and
larger than the paragraph number it is to appear below, using decimals, eg,
to move para 5 to 2nd portal row, change its value to great than 1 and less
2.

To convert to whole numbers, make a script something like this:

exit record
set field counter to 1
go to portal row first
loop
set field paragraph number to counter
set field counter to counter plus 1
go to portal row next exit after last
exit loop

, where counter = a global number field.

Then attach the script to a button above that field in the portal.

Cross references:  In the lease and addenda file, create a field = cross
reference.  In this field, enter the id of the lease and addenda record
that is normally referenced by the current lease and addenda file record.

In the Join file create a field = cross reference which looks up the field
of the same name in the lease and addenda file, based on lease and addenda
record id.

Instead of using the standard text field as the field that is printed,
create a calc field something along the lines of

textfield & " (as stated in paragraph " & join::paragraph no &
Case(
join::paragraph no > paragraph no, " below)", " above)")

, where the join relationship is a self join relationship between cross
reference number and the lease and addenda record ID number.

This way, you will be able to make adjustments to the cross reference no
directly in the tenant file portal if necessary, and still have the
paragraph no and position adjust automatically.

Print the lease from the join file.  In the header and/or footer of the
print layout, include merge fields with tenant details (using reverse
relationship to tenants file).  Make sure the body part is sufficiently wide
to include the largest possible chunk of text.  Set the field and part to
slide up for printing.

Finally, make a script in the tenants file that goes to the related records
(showing only related records) then performs a subscript in the child file
which sorts the records by paragraph number and prints.


Bridget Eley



in article 2004080822331516807%SimonL@JPTGraphicscom, Simon at
SimonL@JPTGraphics.com wrote on 9/8/04 1:32 PM:

> Have a flat file with a few extra tables for look-ups. It prints leases
> and addenda for tenants. For the leases and many addenda, we do merge
> layouts of various lengths, from several dozen paragraphs, and various
> sub-paragraphs, to just a few paragraphs.
> 
> Challenge 1. Manage the paragraph numbering to allow insertions of new
> paragraphs and deletions, and automatic renumbering.
> 
> Challenge 2. Manage the paragraph and sub-paragraph numbers so that
> cross references (like, "as stated in Paragraph 9 above) will change
> when paragraphs are added and deleted.
> 
> I've begun to try a related table with arbitrarily large numbers (1000,
> 2000, 3000, etc) to allow orderly insertions, but I don't get much
> beyond that. Been reading the many-to-many in Help, but haven't been
> able to come up with a working system.
> 
> Is there a plug-in or existing database that does this?
> 
> TIA. Simon
> ===============================
> 
> 

-- 

(to email direct, replace "DOT" with "." and remove ".invalid")

Bonus (this will ensure that the "as stated..." blurb only appears if there
is a paragraph no that has the same text id as the current cross reference):

Textfield  &  
Case(not IsEmpty(cross reference) and IsValid(join::text id), " (as stated
in paragraph " & join::paragraph no &
Case(
join::paragraph no > paragraph no, " below)", " above)"))


in article BD3D4636.6598%bridgeteley@ihugDOTcomDOTau.invalid, Bridget Eley
at bridgeteley@ihugDOTcomDOTau.invalid wrote on 9/8/04 3:18 PM:

> Hi Simon
> 
> Version?
> 
> In version 6 or earlier, you will need a many to many relationship: a master
> file (tenant details), another master file (lease and addenda records from
> which the lease agreements are composed) and a join file (lease and addenda
> records for particular tenants).
> 
> Create a portal in the tenants file to the join file, sorted by paragraph
> number.  Add the lease and addenda details to the join file portal by
> selecting their unique serial number from a popup list referencing the lease
> and addenda file (also reference another field which gives enough
> information so facilitate selection).  Have all the other lease and addenda
> fields lookup details from the lease and addenda file using the unique
> serial number.
> 
> Make a field in the child file called paragraph number, set to autoenter
> status portal row number.  When a new record is made in the join file via
> the portal in the tenants file, this number will autoenter.
> 
> If you also need to reorder paragraphs, make the paragraph number that needs
> to be changed smaller than the paragraph number it is to appear above and
> larger than the paragraph number it is to appear below, using decimals, eg,
> to move para 5 to 2nd portal row, change its value to great than 1 and less
> 2.
> 
> To convert to whole numbers, make a script something like this:
> 
> exit record
> set field counter to 1
> go to portal row first
> loop
> set field paragraph number to counter
> set field counter to counter plus 1
> go to portal row next exit after last
> exit loop
> 
> , where counter = a global number field.
> 
> Then attach the script to a button above that field in the portal.
> 
> Cross references:  In the lease and addenda file, create a field = cross
> reference.  In this field, enter the id of the lease and addenda record
> that is normally referenced by the current lease and addenda file record.
> 
> In the Join file create a field = cross reference which looks up the field
> of the same name in the lease and addenda file, based on lease and addenda
> record id.
> 
> Instead of using the standard text field as the field that is printed,
> create a calc field something along the lines of
> 
> textfield & " (as stated in paragraph " & join::paragraph no &
> Case(
> join::paragraph no > paragraph no, " below)", " above)")
> 
> , where the join relationship is a self join relationship between cross
> reference number and the lease and addenda record ID number.
> 
> This way, you will be able to make adjustments to the cross reference no
> directly in the tenant file portal if necessary, and still have the
> paragraph no and position adjust automatically.
> 
> Print the lease from the join file.  In the header and/or footer of the
> print layout, include merge fields with tenant details (using reverse
> relationship to tenants file).  Make sure the body part is sufficiently wide
> to include the largest possible chunk of text.  Set the field and part to
> slide up for printing.
> 
> Finally, make a script in the tenants file that goes to the related records
> (showing only related records) then performs a subscript in the child file
> which sorts the records by paragraph number and prints.
> 
> 
> Bridget Eley
> 
> 
> 
> in article 2004080822331516807%SimonL@JPTGraphicscom, Simon at
> SimonL@JPTGraphics.com wrote on 9/8/04 1:32 PM:
> 
>> Have a flat file with a few extra tables for look-ups. It prints leases
>> and addenda for tenants. For the leases and many addenda, we do merge
>> layouts of various lengths, from several dozen paragraphs, and various
>> sub-paragraphs, to just a few paragraphs.
>> 
>> Challenge 1. Manage the paragraph numbering to allow insertions of new
>> paragraphs and deletions, and automatic renumbering.
>> 
>> Challenge 2. Manage the paragraph and sub-paragraph numbers so that
>> cross references (like, "as stated in Paragraph 9 above) will change
>> when paragraphs are added and deleted.
>> 
>> I've begun to try a related table with arbitrarily large numbers (1000,
>> 2000, 3000, etc) to allow orderly insertions, but I don't get much
>> beyond that. Been reading the many-to-many in Help, but haven't been
>> able to come up with a working system.
>> 
>> Is there a plug-in or existing database that does this?
>> 
>> TIA. Simon
>> ===============================
>> 
>> 

-- 

(to email direct, replace "DOT" with "." and remove ".invalid")

On 2004-08-09 00:40:28 -0500, Bridget Eley 
<bridgeteley@ihugDOTcomDOTau.invalid> said:

> Bonus (this will ensure that the "as stated..." blurb only appears if there
> is a paragraph no that has the same text id as the current cross reference):
> 
> Textfield  &  Case(not IsEmpty(cross reference) and IsValid(join::text 
> id), " (as stated
> in paragraph " & join::paragraph no &
> Case(
> join::paragraph no > paragraph no, " below)", " above)"))
> 
> 
> in article BD3D4636.6598%bridgeteley@ihugDOTcomDOTau.invalid, Bridget Eley
> at bridgeteley@ihugDOTcomDOTau.invalid wrote on 9/8/04 3:18 PM:
> 
>> Hi Simon
>> 
>> Version?
>> 
>> In version 6 or earlier, you will need a many to many relationship: a master
>> file (tenant details), another master file (lease and addenda records from
>> which the lease agreements are composed) and a join file (lease and addenda
>> records for particular tenants)

-- clipped --

Bridget -- tks much for you detailed reply! I haven't studied it yet, 
but we will today!

We're using 5.5/6 -- our goal is to move to a served application using 
FMP7, Servoy/MySQL or similar.

Currently the tenant data and the document layouts are in the same 
file. The support tables are mostly for generating value lists, like 
all the apt numbers, parking spaces, etc. One problem we face is that 
the leasing documents vary widely even within a small customer base, 
varying from state to state, physical characteristics of the property 
and management policies.

I'd meant to post a small screenshot showing part of what we'd been 
trying, and to say that we'd want to be able to use different 
characters for sub-paragraphs. It shows a state after I'd inserted two 
additional sub-paragraphs after 2a. It's at:  
http://216.87/130.5/leasemanager/ParagraphReorder.pdf

Thanks again. Look forward to trying out your suggestions.

Simon

On 2004-08-09 08:42:50 -0500, Simon 
<SimonL@sphamverboten.JPTGraphics.com> said:

> ParagraphReorder.pdf