>Roi,
>
>I generally avoid macros as they make code difficult to read and understand.
A good practice, they are confusing in most cases.
>
>If two objects in the same container need access to the same property then that property should belong to the container. Doing this removes any need to pass anything back and forth.
Um, I think we are talking about 2 different things. Paul only has 1 object with 1 method and 5 properties.
My first thought was to provide 5 different methods, 1 to minipulate it's own associated property. But the problem is the method code, which gets duplicated 5 times, which isn't so good.
Shouldn't you keep the code in a single method and change the parameters only. Which means you pass the property name to the method right.
I had to do something similar and used ME, I was just wondering if there is a better way.
Roi
'MCP' Visual FoxPro
In Rome, there was a poem.
About a dog, who found two bone.
He lick the one, he lick the other.
He went pyscho, he drop dead!