Hi John,
This is a known bug in VFP 5.0 and I'm sure that there is a MS KB article on it, though I can't give you the ID for it.
I'm sure that it was fixed somewhere along the way, but it could be 5.0a or 6.0. Someone with a better memory will hopefully chime in - I just really wanted to confirm your observation.
Cheers,
Jim N
>I have a question and would like to know if anyone else has ran across this very bizzare behavior on the part of foxpro. My company has an application that is written in foxpro 5.0, however, the vast majority of the screens are old 2.6 screens (most of the code was just imported). On several of these screens we have picklists which are generated with a select statment prior to the screen being displayed.
> Now, you can preselect an item on that picklist by setting the variable associated with the picklist to a item in the list. It seems that whenever the form opens and record number 253 of the cursor is preselected and displayed on the screen, it absolutely kills Foxpro. I've gotten just about every different kind of error message possible ("Field '' not found", "Variable does not exist", "'' is not an object"). The error is bad enough that it usually closes the entire program and boots them back to the windows desktop.
> The only work around that we have found is that if record number 253 is going to be preselected, either don't preselect it OR re-run the same select command, using a different sort order so that item 253 ISN'T preselected. Then it works fine.
> I've spent approximately 5 hours banging my head against the brick wall known as foxpro on this one -- does ANYONE out there know about this bug and, if so, is there a REAL workaround?
> Thanks for your help!!
>
>John Mitchell.
Previous
Reply
View the map of this thread
View the map of this thread starting from this message only
View all messages of this thread
View all messages of this thread starting from this message only