Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
VFP Communications programing
Message
From
02/06/2006 08:57:51
 
 
To
01/06/2006 18:15:31
General information
Forum:
Visual FoxPro
Category:
Windows API functions
Environment versions
Visual FoxPro:
VFP 9 SP1
Miscellaneous
Thread ID:
01123906
Message ID:
01126725
Views:
21
Yeah, it works better that way.
Just wonder, why VB acts differently.
>A messagebox, in that case, will only give you what is presently in the input buffer. Might be 1,2,10 whatever characters. Instead, buffer the data in a form property and bind that to an editbox for testing.
>
>Create a form property - inbuffer.
>Add an editbox to your form - editbox1.
>Set editbox1's controlsource to thisform.inbuffer.
>In your OnComm event add the following code:
>
>thisform.inbuffer = thisform.inbuffer + THIS.INPUT
>
>and tell me what ya got ;-)
>
>>It is MsgBox msComm1.Input in the OnComm event.
>>
>>>There must be at least one line of code somewhere to extract the data from the control - even in VB. Where is it?
>>>
>>>>There is no code. I am using all default values except RThreshold that set to 1.
>>>>Exact same replica works fine in VB.
>>>>
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform