I have had a consistant refresh order problem I could use a solution to.
I place several objects on a form using the form designer. They display in the object picker dialog in say the following order:
o1
o2
o3
...
Later I add, move and delete objects. The order looks like this:
o1
o2
o5
o6
o7
...
Now I need to do validation on say object o2. o2 is phisically below the other objects on the screen, is later in order than the other objects, and is dependant on information in o6 above it (physically). When I use the information from o6 to validate o2 during a refresh I endup validating based on out of date information which has not yet been refreshed. My solution up till now has been to re-refresh o2 in the refresh method of o6 to get it to work correctly - very inefficient and VERY hard to maintain.
I have thought of doing a direct USE on the form SCX and re-ordering the records manually based on their object order but this is clumsy and requires that I remrmber to do it after each form change.
I am looking for a more elegant solution.
Thanks
Terry
It is impossible to make programs idiot proof. Idiots are too cleaver.
MCP( Tcp/Ip )