"SET" variables and Properties...

[William Fields]

I'm having a hard time with the following logic.

SET DELETED = THISFORM.SomeProperty

I've tried a number of variations including...

SET DELETED (THISFORM.SomeProperty)
SET DELETED &THISFORM.SomeProperty
SET DELETED EVAL(THISFORM.SomeProperty)

But nothing works. The only thing I can get to work is this...

LOCAL cSomeVar
cSomeVar = THISFORM.SomeProperty
SET DELETED &cSomeVar

Does anyone know why this is? Am I doing something wrong?

--
William Fields
MCP - Microsoft Visual FoxPro
US Bankruptcy Court
Phoenix, AZ

[Anders Altberg]

>SET DELETED (THISFORM.SomeProperty)
the ( ) are used when the variable is name
>SET DELETED &THISFORM.SomeProperty
& can't be prepended to object references.
>SET DELETED EVAL(THISFORM.SomeProperty)
Try EVAL("thisform.someproperty")
It will work if the value is "YMD" and you SET DATE TO
EVAL("Thisform.Text1.Value") or EVAL("Thisform.DateProperty")
but not with value = "ON" and SET TALK.
-Anders

.. "William Fields" <Bill_Fields@azb.uscourts.gov> wrote in message
news:3929c0fe$1@news.devx.com...
> I'm having a hard time with the following logic.
>
> SET DELETED = THISFORM.SomeProperty
>
> I've tried a number of variations including...
>
> SET DELETED (THISFORM.SomeProperty)
> SET DELETED &THISFORM.SomeProperty
> SET DELETED EVAL(THISFORM.SomeProperty)
>
> But nothing works. The only thing I can get to work is this...
>
> LOCAL cSomeVar
> cSomeVar = THISFORM.SomeProperty
> SET DELETED &cSomeVar
>
> Does anyone know why this is? Am I doing something wrong?
>
> --
> William Fields
> MCP - Microsoft Visual FoxPro
> US Bankruptcy Court
> Phoenix, AZ
>
>
>
>
>
>

[Nancy Folsom [MS FoxPro MVP]]

"William Fields" <Bill_Fields@azb.uscourts.gov> wrote in message
news:3929c0fe$1@news.devx.com...
> I'm having a hard time with the following logic.
>
> SET DELETED = THISFORM.SomeProperty

Use macro expansion for this, but you have to set a memvar equal to your
property, first.

> SET DELETED (THISFORM.SomeProperty)

That's named expression syntax, which doens't work in this context.

> SET DELETED &THISFORM.SomeProperty

You can't macro expand a property. Specifically, since the first period
after the macro & signifies the end of the macro expression, VFP looks for
some string variable called "thisform" to substitute and prefix to
"someproperty".

> SET DELETED EVAL(THISFORM.SomeProperty)

I don't understand the mechanism here of exactly what goes on, but if the
property equals "ON", then doing EVAL on, the app will look for a memvar by
the name of ON. In other words (I guess) EVAL must result in an expression,
which the literal ON isn't.

[William Fields]

Yes, from the other responses I've gathered that the only way to
consistently use form properties to hold values for SET commands is to
create a memvar first equal to the contents of the form property, then macro
expand it.

IE...

LOCAL cSomeVar
cSomeVar = THISFORM.SomeProperty
SET DELETED &cSomeVar


Thanks.

--
William Fields
MCP - Microsoft Visual FoxPro
US Bankruptcy Court
Phoenix, AZ


"Nancy Folsom [MS FoxPro MVP]" <nancy_folsom@hotmail.com> wrote in message
news:3929de90@news.devx.com...
> "William Fields" <Bill_Fields@azb.uscourts.gov> wrote in message
> news:3929c0fe$1@news.devx.com...
> > I'm having a hard time with the following logic.
> >
> > SET DELETED = THISFORM.SomeProperty
>
> Use macro expansion for this, but you have to set a memvar equal to your
> property, first.
>
> > SET DELETED (THISFORM.SomeProperty)
>
> That's named expression syntax, which doens't work in this context.
>
> > SET DELETED &THISFORM.SomeProperty
>
> You can't macro expand a property. Specifically, since the first period
> after the macro & signifies the end of the macro expression, VFP looks for
> some string variable called "thisform" to substitute and prefix to
> "someproperty".
>
> > SET DELETED EVAL(THISFORM.SomeProperty)
>
> I don't understand the mechanism here of exactly what goes on, but if the
> property equals "ON", then doing EVAL on, the app will look for a memvar
by
> the name of ON. In other words (I guess) EVAL must result in an
expression,
> which the literal ON isn't.
>
>
>

[Fred Taylor]

About your only other option is to store some kind of conditional check and
do it with an IF or DO CASE structure:

IF condition="ON"
SET DELETED ON
ELSE
SET DELETED OFF
ENDIF

- or -

DO CASE
CASE condition="ON"
SET DELETED ON
CASE condition="OFF"
SET DELETED OFF
OTHERWISE
MESSAGEBOX("Unknown condition!")
ENDCASE


Fred

William Fields wrote in message <392ab062@news.devx.com>...
>Yes, from the other responses I've gathered that the only way to
>consistently use form properties to hold values for SET commands is to
>create a memvar first equal to the contents of the form property, then
macro
>expand it.
>
>IE...
>
>LOCAL cSomeVar
>cSomeVar = THISFORM.SomeProperty
>SET DELETED &cSomeVar
>
>
>Thanks.
>
>--
>William Fields
>MCP - Microsoft Visual FoxPro
>US Bankruptcy Court
>Phoenix, AZ
>
>
>"Nancy Folsom [MS FoxPro MVP]" <nancy_folsom@hotmail.com> wrote in message
>news:3929de90@news.devx.com...
>> "William Fields" <Bill_Fields@azb.uscourts.gov> wrote in message
>> news:3929c0fe$1@news.devx.com...
>> > I'm having a hard time with the following logic.
>> >
>> > SET DELETED = THISFORM.SomeProperty
>>
>> Use macro expansion for this, but you have to set a memvar equal to your
>> property, first.
>>
>> > SET DELETED (THISFORM.SomeProperty)
>>
>> That's named expression syntax, which doens't work in this context.
>>
>> > SET DELETED &THISFORM.SomeProperty
>>
>> You can't macro expand a property. Specifically, since the first period
>> after the macro & signifies the end of the macro expression, VFP looks
for
>> some string variable called "thisform" to substitute and prefix to
>> "someproperty".
>>
>> > SET DELETED EVAL(THISFORM.SomeProperty)
>>
>> I don't understand the mechanism here of exactly what goes on, but if the
>> property equals "ON", then doing EVAL on, the app will look for a memvar
>by
>> the name of ON. In other words (I guess) EVAL must result in an
>expression,
>> which the literal ON isn't.
>>
>>
>>
>
>