You could check out my ChkStr routine. It's a string search that will
drill through objects/events on a form and will report where it finds
the string(s). By process of elimination you can determine where it
didn't find the string.
You could use the ChkStr routine to search for any string even if it's
in a COMMENT....
It also stores the results of the string search in a dbf -- so, when you
know you've got a clean .scx with ALL of the code in it you can run the
ChkStr Routine, save the resulting dbf and use it later to compare to
the dbf produced during subsequent checks.
Cheers;
Chet
Hal Kaplan wrote:
=> Hal:
=> Thanks for the suggestion.
=> So if I understand this technique I could define a variable
=> (say gnCode_verify) as public and in every click() event I
=> could say gnCode_verify = 0. I would need know how many
=> times I used it and have a list of where it is so when the
=> 'Code Reference Tool' tells where it is I could cross
=> reference the list. And when the 2 don't match I have a
=> reference of where I need to put the code back in.
=> I hope the order for VFP9 gets here soon...
=> Regards,
=>
=> Jack Skelley
=>
Exactly. And there could very well be something that is already there that you
can use.
Is the tool available in version 8?
You probably won't need it in 9 but it might be worthwhile for quality control.
HALinNY
[excessive quoting removed by server]
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/profox
OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech
** All postings, unless explicitly stated otherwise, are the opinions of the
author, and do not constitute legal or medical advice. This statement is added
to the messages for those lawyers who are too stupid to see the obvious.
