Tracking changes made to an address block of info in a database

[Ken Doucet]

Josh: TESO - TextEntrySuper0bject?

		I will set up a form for editing this address block. I will check out the
functions/procedures in the documentation to see if I can grasp/implement
your suggestion.

Craig - I realize that changing ont to not would not change character count
but in most cases this wouldn't be the scenario. The vast majority of
changes would trigger a count difference and this "risk" is small compared
to benefits of catching the majority of legit changes.


Thanks

Ken


Message: 2
Date: Wed, 05 Mar 2008 15:23:48 -0500
From: Josh Davenport <josh.davenport at verizon.net>
Subject: Re: Tracking changes made to an address block of info in a
	database
To: "Panorama Questions & Answers \(Discussion\)" <qna at provue.com>
Message-ID: <1A92A091-22A0-4100-93C2-084CED1CA035 at verizon.net>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed

Assuming the address is usually edited from a form you control, and
not form random places:

Use one or more TESOs  to do the editing of the fields you wish to
time stamp.

Attach a procedure to the TESO, and run the procedure as a handler.
Check the "focus" box, so that the procedure is called BEFORE data is
changed.

In the handler procedure, trap the trigger with
	case info("trigger") beginswith "focus"

Use a fileglobal to store the old data. Since you only need to store
the data between entering
the text editor and leaving the text editor, if the record isn't too
big, you could use:
	fgOldData=exportline()

when you exit the text editor

case info("trigger") match "oStreetAddress"

local newData
newData=exportline()
if fgOldData <> newData
	shortcall doTimeStamp
endif

You can simplify the code by using smart naming conventions for your
objects,
or if this is all that needs to be done here just use "defaultcase"

if your records are large, instead of exportline(), build a custom
concatenation
	fgOldData=field1+field2+field3
	The advantage of exportline() is that is takes care of all data
types for you


BTW, I haven't posted for a while, but I have been managing a
migration from
version 3 to version 5.5 enterprise. Seems to be going well. I will
post some info on
my strategy soon in case anyone is interested. In particular, I have
a reasonable method
for updating shared files.

Josh


Message: 8
Date: Wed, 5 Mar 2008 14:46:06 -0800
From: Craig McPherson <cdpublishing at qwestoffice.net>

that doesn't seem like it would work; correcting 'ont' to 'not' would
not change the character count...
Craig McPherson

------------------------------

_______________________________________________
Qna mailing list
Qna at provue.com
http://provue.com/mailman/listinfo/qna


End of Qna Digest, Vol 3, Issue 9
*********************************