O$ DF problems

[Stephen Miller]

Steve and all

If you are using ndf should you be using the ODT technology to overcome
these problems.

The ODT structure can export data file damage so I would be wary about
using that.

The sequence number issue - even if you use named primary and foreign keys
instead please note that the sequence field always exists and to see the
value all you need to do is use notation to create it.

Quick check usually only  shows problems that can be repaired by OMNIS on
the fly. Really you should use long check or nothing.

In you case if it is an index problem why dont you try drop and rebuild
indexes on a COPY of the df1?


Regards

Stephen Miller



On Thu, May 10, 2012 at 8:03 PM, <Wizardcompserv at aol.com> wrote:

> The main reason I have found for duplicate indexes is that 'write behind
> cashing' is on on the computers - this means that the information is
> locally
> cashed and not written back until Windows decides it would like to or the
> user  logs out.
>
> I give my customers a document which tells them how to unset it and that it
>  will corrupt the database and I will charge them to sort it out!!!
>
> Kind  Regards
> Wendy Osbaldestin
> Wizard Computer Services
> _www.wizardcompserv.co.uk_ (http://www.wizardcompserv.co.uk/)
> Tel:  01260271647
>
>
> In a message dated 10/05/2012 10:58:47 GMT Daylight Time,
> omnis at smartway.ch
>  writes:
>
> one with  a corrupted index that allowed duplicate sequence  ids
>
> _____________________________________________________________
> Manage your list subscriptions at http://lists.omnis-dev.com
>



-- 
*Kind Regards

Stephen Miller

+61 (0)415 968048

Skype: Stephen.Miller.1958

Work Phone: 08 6213 5697  *

*Work E-mail: Stephen.Miller at health.wa.gov.au; *