Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Text box does not always reflect controlsource
Message
From
11/11/1997 14:49:53
Edward Crawford
City Facilities Management
Glasgow, United Kingdom
 
 
To
11/11/1997 13:41:45
General information
Forum:
Visual FoxPro
Category:
Coding, syntax & commands
Miscellaneous
Thread ID:
00059394
Message ID:
00059579
Views:
38
>>>>>>I have a list box with the .ControlSource = "Contact.ContactId". Contact has about 100 records in it. I also have three textboxes who have their .ControlSources set to "Contact.Contact", "Contact.Phone", and "Contact.Fax". If I click on anyone of the first 25 items in the list box, the data in the text boxes chages as they are supposed to. If, however, if I click on items 26 -100, the data in the test boxes will not change. If you look at the Data Session, it shows that the pointer is on the correct record. You can also click on the text box and it will change to the right data. I tryed to Refresh() the text boxes in the List.Click() event, but this doesn't work. Why is this happening?
>>>>>>
>>>>>>-Ed
>>>>>
>>>>>Refresh the tesxtboxes in the listbox.interactive change event, instead of the click.
>>>>
>>>>Erik,
>>>>
>>>>I still got the same behavior.
>>>>-Ed
>>>
>>>Do the textboxes refresh with a manual refresh (like from a test button with thisform.refresh in the .click)?
>>>If so, have you watched the code in the debugger to make sure your refresh is firing?
>>
>>I have an Account selection class that sits on a form. I also have a page frame on the form. As I turns the pages of the page frame, the Account Selection class stays visible so I can access it from any page and change accounts. On the last however, I do not want the option of changing accounts, so in the Activate Method of the page I set the Account Selection class's .Visible property to .F. I have texboxes that are partialy covered by the invisible class. I think that this class is interfering with the controls on this page since they are behind the invisible class. I would think that .Visible = .F. would keep it from interacting with the page, but aparently there is a problem.
>>
>>-Ed
>
>This seems easy enough to test: move the selection class out from in front of the suspect textboxes, and see if the situation changes.

Yeah, I was absolutely sure that this was the cause, I just wrote you to tell you what it was. However, after moving it from behind the class it still has the problem. I'll just figure out a different way to accomplish what I am trying to do.

-Ed
Previous
Reply
Map
View

Click here to load this message in the networking platform