>hi all,
>i have a error message(table has no index order set)
>select book1
>index on no to kkk,
>any idea,thanks
That is strange: This error usually appears when you try to
use the index, not when you try to
create it. Or did the error appear later - for example, when you try a SEEK?
Anyway, I would suggest that - most of the time - you create permanent indexes. In your example, if your field is called "no", the index might also be called "no":
index on no tag no
If you work like this, all indexes are combined in a single file (same file name as the table, but with extension CDX). This file is opened automatically with the table, so your indexes will usually remain updated.
Difference in opinions hath cost many millions of lives: for instance, whether flesh be bread, or bread be flesh; whether whistling be a vice or a virtue; whether it be better to kiss a post, or throw it into the fire... (from Gulliver's Travels)
