Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Kickin around memory variables?
Message
From
24/05/2001 12:57:51
Cetin Basoz
Engineerica Inc.
Izmir, Turkey
 
 
To
24/05/2001 12:49:16
Charlie Schreiner
Myers and Stauffer Consulting
Topeka, Kansas, United States
General information
Forum:
Visual FoxPro
Category:
Coding, syntax & commands
Miscellaneous
Thread ID:
00510941
Message ID:
00511040
Views:
19
>Hi Cetin,
>
>>2)Yes you should. If you don't use m. and same name exists in current alias it takes precedence. ie:
>>m.employeename = 'me'
>>would work while :
>>employeename = 'you'
>>would fail if current table had a field named employeename.
>
>employeename = 'you' is just fine. EmployName becomes a variable if it wasn't already. It's the only when ambiguity exists, as it does here on the right side of these assignments->
>CREATE CURSOR This (You C(15))
>INSERT INTO This (You) VALUES ("Charlie")
>
>You = "Cetin"
>EmployName = m.You
>vs.
>EmployName = You
>vs.
>EmployName = This.You
>vs.
>EmployName = m.This.You && Assuming a property named You.

Charlie,
I think you got me wrong more truely I said it wrong.

CREATE CURSOR This (You C(15))
INSERT INTO This (You) VALUES ("Charlie")
You = "Cetin"
I tried to mean :)
m.You # you

Regards
Cetin
Çetin Basöz

The way to Go
Flutter - For mobile, web and desktop.
World's most advanced open source relational database.
.Net for foxheads - Blog (main)
FoxSharp - Blog (mirror)
Welcome to FoxyClasses

LinqPad - C#,VB,F#,SQL,eSQL ... scratchpad
Previous
Reply
Map
View

Click here to load this message in the networking platform