Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Index on View
Message
De
13/11/1998 14:52:59
Rebecca Stottlemire
Kansas State Department of Commerce
Topeka, Kansas, États-Unis
 
 
À
13/11/1998 14:21:39
Information générale
Forum:
Visual FoxPro
Catégorie:
Autre
Titre:
Divers
Thread ID:
00157416
Message ID:
00157514
Vues:
16
>>>>I'm trying to set indexes on a view that is browsed in a grid, so that the user can change the order in which they see the data. I have it in the load of the form, and it steps through the code just fine, but the order of the view isn't changed. The session view doesn't show any order set or anything, like nothing has happened. I also repeated the indexing code after the Requery so that I wouldn't loose indexes, but with no luck. Any ideas?
>>>>Thanks,
>>>>Becky
>>>
>>>Could you post your code?
>>
>>Well, the truth of the matter is that I just gave up on the indexing views. I created two separate view, each ordered differently. Then when the user clicks the radio button on screen to change order, I requery the newly requested view and stick it in the grid. This works fine. I don't know why the index didn't work. I had something like:
>>SELECT (thisform.cTable)
>>INDEX ON lastname+frstname+catcode+skilcode TAG nameorder
>>INDEX ON skilcode+catcode+lastname+frstname TAG skilorder (trims on the names)
>>SET ORDER TO nameorder
>>
>>Thanks
>>Becky
>>
>>Lucky me, I'm going to Dallas all next week for COBOL training, yuk!
>
>I don't think that Cobol will help here :).
>What can I say? It should work... so something is wrong. Do you really set buffering=3 on views? Do you refresh grid after SET ORDER? If you wouldn't have tags then SET ORDER should bomb your application. May it indicate that you have problems with error handler? (which blanks out all errors?)

Hi,
I have buffer mode 1 in the views (in the data environment of the form), then buffer mode 2 on the form itself. I'm sending SQL updates with TABLEUPDATE and everything seems to work fine. I also have a routine for ON ERROR that just sends the error message to a messagebox and returns F. That seems to work fine, too.
Thanks for your help. They're testing it now, so I'm hoping for the best.
Becky
Précédent
Répondre
Fil
Voir

Click here to load this message in the networking platform