Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
ComboBox woes
Message
From
26/02/1999 11:20:13
 
General information
Forum:
Visual FoxPro
Category:
Other
Title:
Miscellaneous
Thread ID:
00190932
Message ID:
00191969
Views:
25
OK, FWIW, I have discovered the cause of the problem. It's my version of combo that's causing the problem, but it's not apparent at first, that's why I questioned whether I was even doing the grid right or not (my first time using grids).

A friend of mine sent me an old demo-type program written by Drew Speedie to illustrate some concepts ... there it was in black-and-white, just what I needed to do ... problem was that I pretty much had been doing everything that Drew said to do, with a few minor differences (one difference being that he didn't have *any* fields bound at all!!) I changed things around to fit his descriptions and guess what? it still didn't work. So now I figured it was probably my custom cbo class that was the culprit. I had tried this way back in the beginning with the standard, Foxpro-issue cbo, but still had problems because I still hadn't set up some other things correctly. I have a QuickFill cbo, grabbed from an article in FPA by Tamar Granor and modified just a bit more to fit my needs. Sure enough, when I put my cbo in Drew's grid as the current control, it started doing weird things again.

So, now I guess I need to come up with another custom cbo class for use in grids, problem is I'm still not sure what's wrong with the one I was using. The weird behavior doesn't start until you've moved the focus at least once into the cbo and then out of the cbo column. Until you get into the cbo, everything is fine and then as long as you remain in the cbo, everything's fine. It's once you leave the cbo and get into the next column that things start to go haywire. If you move up or down a row (sometimes it takes more than a few rows), the record pointer in the child table doesn't move. It takes issuing the two commands: "SELECT ParentTable GOTO RECNO()" once and sometimes twice to get the record pointer in the child table to behave. Very, very strange ... and until you manually put the record pointers back in sync with this method, the child record pointer refuses to move, no matter what. I was thinking of just "refreshing" the record pointers everytime (didn't seem to work in the AfterRowColChange, so I'm not sure where to put it), but that seems a bit kludgy ... I should probably use a different cbo instead.

Whew ... sorry to be so wordy (if anyone has stayed with me thru this diatribe)! Anyone have any comments, suggestions or anything?????

Bonnie
Bonnie Berent DeWitt
NET/C# MVP since 2003

http://geek-goddess-bonnie.blogspot.com
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform