Terry,

I only read today's stuff, so you may have already answered this. . .

Do you have UNIQUE in the index(es) in question?

Good lick,

Jim N

>>>
>>>I was able to do some more research on this after I sent my first letter. It seems to be something along the lines you are stating. I found some of my combos worked - refrencing the exact same maintenance form. So, I made every single property and method the same between one that did work and one that didn't - no effect. Then I changed the Read Only flag on my default data session ( your solution ). Some then worked but others still failed. I then examined the tables directly. Sure enough the data was there just not in the index and I noticed by cycling the Set deleted On/Off I could get the data to appear and disappear. Finaly I packed and or reindexed the files and the data appeared fine. I can't do this in the production environment as it requires exclusive access to the file which by definition I don't have.
>>>A this point I am again stuck.
>>>
>>>Thanks
>>>Terry
>>
>>Ok, I've read through your discussion with Evan.
>>
>>Have you made all of your files updatable in the default DS? That should help, but perhaps there is something else going on.
>
>YES
>
>>
>>Do you think that some of your CDX files are still not being updated?
>
>YES
>
>>
>>By including ".not. deleted()" in your tags you are doing the same thing as "SET DELETED ON". Therefore I assume you are running with "SET DELETED OFF". I would think you would not want to do both.
>
>No I am running with set deleted on. This is a hold over from some primary index filters I used. If I didn't include the !deleted() part when I created new records that may have duplicated previously deleted ones the end user got index violation errors they could not understand or deal with. So, I use !deleted() on all candidate and primary indexes.
>
>>
>>If you start with a clean file (packed and reindexed) and use your update form, what is the first problem that you can notice?
>
>When I enter a new record it does not show. I open the table with the index set and it is not there in browse but if I turn off the index it is there. Also, if I happen to create a duplicate ( as the first one didn't show ) and then pack or reindex it deletes all the tags from the one that had the duplicate on ( ie if the tag is say County and is candidate, all tags alphabetically above County are removed when I reindex - if there is a duplicate county. I have to recreate all the indexes over. ).
>
>>
>>Peter
>
>
>This is getting irritating.
>
>Terry