MB Software Solutions, LLC wrote on 2010-03-29:

>

> Thanks, Frank, Tracey, and others. It's not a top-level form. I'm

> finding some other unholy behavior so I think I'll just nuke and re-

> build this form. It's very small and so terminating this pest is not

> a huge loss. I do appreciate the feedback though.

>

> Did you ever get some things in VFP that just can't be explained?

> This seems to be one of them. I've got code releasing the form and

> yet when I call it again, it's got the same values I had from the original

call.

> It's almost like it's not residing in memory as expected (nor

> releasing as expected). Freaky.

>

>

Mike,

Grigore showed a great example of this behavior a couple years back.

Christof explained it at a SWFox.

Create a class with a property that gets set to SYS(2015), instantiate it a

few times and run it.

Clearing the FoxPro session and restarting it changes the SYS(2015). Or

issuing a CLEAR ALL.

o1 = CREATEOBJECT("myTest")

?o1.sys2015

o2 = CREATEOBJECT("myTest")

?o2.sys2015

DEFINE CLASS myTest as CUSTOM

SYS2015 = SYS(2015)

ENDDEFINE

Tracy Pearson

PowerChurch Software

_______________________________________________

Post Messages to: ProFox@leafe.com

Subscription Maintenance: http://leafe.com/mailman/listinfo/profox

OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech

Searchable Archive: http://leafe.com/archives/search/profox

This message: http://leafe.com/archives/byMID/profox/000101cacf44$792f9e10$6b8eda30$@com

** 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.