> >
> > Reading the help file did not answer any of my 4 asked question.
>
> Then I am afraid that I cannot help you either.
>
> Since the Help file explicitly tells you that you cannot re-use the names, that you cannot declare them as anything other than PUBLIC or PRIVATE, and warns you that VFP maintains them automatically - in other words it will overwrite any changes you may try and make. That pretty much covers the "questions"
and look who is advising to read and believe the help file. ;)
can I have your bless to use Public variable to hold form object. It is also mentioned in help file. :)
I guess if have you a sword, you take that help file and make it small pieces. (lol)
> May I remind you of the saying that "a fool can ask questions that a wise man cannot answer".
You mean, I should not ask Hard Question?
> Now, I am not calling you a fool, or trying to make fun of you, but I am saying that I your questions are based on assumptions that are not valid and so are impossible to answer because their underlying premise is incorrect.
I said I "guess it is related to OOP". I really don't know. that is what i am trying to understand.
> For example, you made the comment about System Variables and OOP - but you must remember that VFP has its roots in FoxPro, and before that in FoxBase - a competitor for dBase III - which existed as a DOS product long before the advent of Windows. An awful lot of things in VFP are still there from those roots (for backward compatibility) and have nothing whatever to do with current VFP versions - system variables are a good example and, as is noted in the help file
> Quote:
> Recent Visual FoxPro features have replaced the functionality of many system variables.
> End Quote:
>
> Your quest for knowledge is laudable but you are in danger of starting out from a false premise. It seems to me that you are assuming that VFP is a coherent and logical whole. But it isn't! In reality it's just a mish-mash of functionality and techniques that have evolved over 20+ years.
> It is so far from its original design that it is hard to remember that it was originally written to be primarily a "dot-prompt" driven interactive tool.
>
> You simply cannot assume that a system variable like "_Pageno" are in any way related to the functionality of VFP 9.0 because it isn't, that one goes all the way back to FoxBase 1.0 in the mid 1980s and hasn't changed since then.
System variable is part of vfp9 (my current version). and vfp9 support OOP. My questions is trying to understand how and what level OOP deals with it.
If there will be
VFP.NET version, and these System variable are included. I will ask the same question.
>
> Regards
> Andy Kramek
> Microsoft MVP (Visual FoxPro)
>
Tightline Computers Inc, Akron Ohio, USASecret #1 (Learn it from Christoph)
#DEFINE xFamily Karmak
? "Hi Andy xFamily"
? [Hi Andy xFamily]
[] <-- is a acting as substitution? where it mentioned in the help file?
Secret #2 (Learn it from Glenn)
in dll, if you have RETURN DATE() it will return DATETIME(), where it mentioned in the help file?
Secret #3 (Learned from Anil Shama)
*** myfile.h
#DEFINE xName "Testing"
*** startup.prg
INCLUDE myfile.h
DO FORM FORM1 && FORM1 Default data session
DO FORM FORM2 && FORM2 Private Data Session
*** Form1.Load
? xname && return "Testing"
*** Form.Load
? xName && Return Error
Secret #4 (I discover it)
*** Form.Init
This.caption = "New Caption" && Is Valid
This . Caption = "New Caption 2" &&Is also Valid although there is spaces between object and property
All the above secrets are not mentioned in the help file.
Finally, Help file is just a "Help File". if you want to reveal a secret, ask experts and the wise guys or discover it your self.
Last time, you attacked the help file as if the help file killed someone dear to you, and now you advising me STRONGLY to stick with the help file? I wonder.
If the answer is not in the help file, it is with someone else.
Samir R. Ibrahim
Good things Take time, Great things happend all at once.My WebLogMy Website:
www.cdcity.org