Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Ctod() weirdness
Message
From
16/08/2015 12:00:27
Lutz Scheffler
Lutz Scheffler Software Ingenieurbüro
Dresden, Germany
 
 
To
15/08/2015 07:14:48
Dragan Nedeljkovich
Now officially retired
Zrenjanin, Serbia
General information
Forum:
Visual FoxPro
Category:
Coding, syntax & commands
Environment versions
Visual FoxPro:
VFP 9 SP2
OS:
Windows Server 2012
Network:
Windows 2008 Server
Database:
MS SQL Server
Application:
Web
Miscellaneous
Thread ID:
01623085
Message ID:
01623460
Views:
69
>>>>If you do
>>>>
>>>>SET CENTURY TO
>>>>?SET("Century"),SET("Century",1),SET("Century",2)
>>>>
>>>>is the output the same?
>>>
>>>Nope, now I'm getting
>>>ON 19 65
>>
>>That's strange. Shure you do not anything else with SET CENTURY on startup? Because 19 50 means the 50 needs to be set somehow.
>>What happend if you create a numb private form and put into init event:
>>
>>?SET("Century"),SET("Century",1),SET("Century",2)
>>SET CENTURY TO
>>?SET("Century"),SET("Century",1),SET("Century",2)
>>
>>and run the form?
>>because that is what should be default.
>
>
ofrm=createobject("daForm")
>ofrm.show()
>
>DEFINE CLASS daForm as Form
>windowtype=1
>
>
>PROCEDURE show()
>dodefault()
>this.Print(textmerge([<<SET("Century")>> <<SET("Century",1)>> <<SET("Century",2)>>])+chr(13))
>SET CENTURY TO
>this.Print(textmerge([<<SET("Century")>> <<SET("Century",1)>> <<SET("Century",2)>>]))
>ENDDEFINE 
>
>shows ON 19 65 both times.

So the question is, why on VFP startup you get 19 50?
Words are given to man to enable him to conceal his true feelings.
Charles Maurice de Talleyrand-Périgord

Weeks of programming can save you hours of planning.

Off

There is no place like [::1]
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform