We have been having indexing problems lately. In fact I was able to locate some of our weirdo problems as being indexes that actually pointed to the wrong records! Talk about disastrous! We also have large files 1-2Gb with indexes of 200Mb+. This seems to exacerbate the problem. But it has also happened ing some smaller tables. All I can tell is that because it isnt client-server and so much of the index travels down the wire that something goes wrong - regularly. We are also regularly rebuilding indexes but it is a disappointing situation. It is one thing for an index to be physically corrupted and a message telling you that; it is quite another for an index to point to the wrong record without any advice! Is this something new with SP2? I dont recall index problems being so prevalent before.
I'm trying to convince my client to do a complete rewrite in VB.NET and this is one of the reasons. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jean Haidar Sent: Wednesday, 10 December 2008 6:13 AM To: [email protected] Subject: Re: VFP index corruption the size of the .DBF is 1.1 gig and the cdx is 158 Mg that would be be an issue? Jean ________________________________ From: Fred Taylor <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Sent: Tuesday, December 9, 2008 1:15:22 PM Subject: Re: VFP index corruption Make sure the size of your .CDX file isn't the issue. With 29 tags and that much data in the table, you may have gone over the 2GB file limit. Fred On Tue, Dec 9, 2008 at 12:11 PM, Jean Haidar <[EMAIL PROTECTED]>wrote: > The data reside on Citrix Server and it is not eady to request changes from > the Citrix Team? > > we are rebuilding the index every few days > > If it is a bad block? don't you think this error would pop up in > another Index File or some other DBF file? > > Thanks, > Jean > > > ________________________________ > From: Michael Madigan <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Sent: Tuesday, December 9, 2008 12:57:11 PM > Subject: Re: VFP index corruption > > 1. Check the event log of the computer that holds the data to see that > there are no bad blocks or other disk problems in the event logs. > > 2. Make sure opportunistic locking is turned off on the server. > > 3. Run scan disk > > > [excessive quoting removed by server] _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[EMAIL PROTECTED] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
