Evan,
I'm surprised -- I've never seen this work at all in SQL.
I always approach this by putting the values into local variables:
local lcLactName, lcFirstName
lcLastName = this.parent.txtLastName.Value
lcFirstName = this.parent.txtFirstName.Value
UPDATE ;
vwSubscriberOne ;
SET ;
cLastName = m.lcLastName, ;
cFirstName = m.lcFirstName, ;
etc. etc. ;
WHERE somecondition
Cheers,
Andrew
>Hi gang,
>
>SET DEVELOPER FRUSTRATION TO HIGH
>
>I'm pulling what few hairs I have left out on this one. I have an UPDATE-SQL command, executed from a command button on a page of a pageframe, that alters a record in an updateable local view, with multiple items to SET, as follows:
>
>
>loParent = THIS.Parent
>
>UPDATE ;
> vwSubscriberOne ;
> SET ;
> cLastName = loParent.txtLastName.Value, ;
> cFirstName = loParent.txtFirstName.Value, ;
> etc. etc. ;
> WHERE somecondition
>
>The command refuses to execute, telling me that "Alias txtLastName is not found". A similar INSERT-SQL command, in the same method of the same command button, uses the *identical* loParent.txtLastName.Value reference without a complaint.
>
>What the @#$%^&* am I missing here?
>
>TIA,
If we were to introduce Visual FoxBase+, would we be able to work from the dotNet Prompt?
From Top 22 Developer Responses to defects in Software
2. "It’s not a bug, it’s a feature."
1. "I thought I fixed that."
All my FoxTalk and other articles are available on my
web site.
Unless specifically identified otherwise, anthing posted here is purely my opinion and may or may not reflect the policies or practices of Microsoft.