Remove the properties first.
If the compiler complains that the property does not exist anymore,
then, at least, you have to change its name to avoid conflict.
In the end, all goes fine.
Le 21 juil. 06 à 23:54 Soir, Russ Jones a écrit:
On Jul 20, 2006, at 7:53 PM, Norman Palardy wrote:
And finding out what is used is as simple as comment them all out
and recompile and uncomment the ones that the compiler complains
about. The rest remain commented out
This usually works ok - but watch out for overlapping scope.
For instance:
If you have a local, dim xyz as integer and everything works ok.
Now you comment the local dim xyz out, but don't notice you also
have a property named xyz,
your references compile ok, but you are now altering the value of
the property,
where before you were using a local.
Those side effects can be tricky to debug, mainly because you don't
expect them.
Russ
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
