Odd behaviour from timeModified

[Matt Mower]

Hi Sam,

Thanks for replying (sorry I only just spotted your message).

Samuel Reynolds wrote:

> As long as I remember, it has returned false for "basic" types
> (string, address, boolean, etc.), and only returned the actual
> modification date/time for more complex types.
> 

Okay thanks for the explanation.  Now I read the doc page again I can 
see the final example does show this.  Mea culpa.

> It raises a scriptError if you pass it an address to a non-existent
> location, but always returns a value (either time or true/false)
> if you pass it a valid address.
> 

Hmm...  My recollection is that I was always using the address of a 
table object, but seeing different return values.  I need to go back and 
walk through the code again and make sure of what I was seeing.

Thanks,

Matt