Information générale
Catégorie:
Base de données, Tables, Vues, Index et syntaxe SQL
>I've a table (Orders.dbf) which has a bunch of indexes. Several are based on DateTime fields (Order_Date, Print_Date, Invoiced, Close_Date). The Invoiced tag seems to be corrupt.
>
>I open the table (about 3000 records). Set the index to Invoiced. Browse Normal.
>
>As I scroll (pgdn) thru the table I reach a spot where the browse behaves strange.
>The browse shows about 20-25 records.
>The record at the top (visually) is Order_ID 28.
>The next record (visualy) is Order_id 1.
>The record one up from the bottom (visualy) is Order_id 27.
>The record at the bottom (visually) is Order_id 28. hmmm???? It looks like a reflection of the top record.
>
>As I try to pgdn I just cycle on this set of records.
>As I try to walk into the bottom record with the down arrow key, (from Order_ID 27), I end up at the top of the browse.
>If I try to click in the record at the bottom...I end up at the top of the browse.
>If I try to double click in the record at the bottom...I end up with the double click behaviour happening on the record at the top of the browse.
>
>
>Is this indeed a corrupt index?
>Should I not index directly on a Date or DateTime Field?
>Should I use DTOS(myDateField)?
>Should I use TTOC(myDateTimeField,1)?
>
>
>TIA,
>Rick
Rick
Yes, this is definately a corrupted index. I have seen index corruption go away when the index was changed from a datetime field to ttoc(myDateTimeField, 1) as you suggest. Let us know if this works. Do you have any ideas on what might be affecting this index? A simple datetime index normally works, although as we both have seen ... under some circumstances it doesn't.
Bob
Précédent
Suivant
Répondre
Voir le fil de ce thread
Voir le fil de ce thread à partir de ce message seulement
Voir tous les messages de ce thread
Voir tous les messages de ce thread à partir de ce message seulement