Michael, Hmm, it does seem a strange problem then and obviously not something simple.
Just a stab in the dark here, but do you have any indexes based upon purely numeric fields? I remember having a problem some time ago now when these fields went into overflow (the old "*"'s problem) and created havoc to the index files. Just a thought. Dave -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Michael Madigan Sent: 15 May 2012 12:20 To: ProFox Email List Subject: Re: I have to be able to browse the whole database, but it causes corruption This server is before SMB2. ________________________________ From: Dave Crozier <[email protected]> To: ProFox Email List <[email protected]> Sent: Tuesday, May 15, 2012 6:36 AM Subject: RE: I have to be able to browse the whole database, but it causes corruption Michael, I guess you are using SMB2 then, for which there are KNOWN problems. Personally I would revert back to SMB1 (standard Samba) if this is the case. I know from personal experience that oplocks on SMB2 can cause index file corruption due to the different way they are handled from SMB1. Dave -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Michael Madigan Sent: 15 May 2012 11:32 To: ProFox Email List Subject: Re: I have to be able to browse the whole database, but it causes corruption I'm using a Linix-based NAS. It's definitely not as fast as a server, but it's been fast enough based on how we had been doing things and unbelievably reliable. ________________________________ From: Dave Crozier <[email protected]> To: ProFox Email List <[email protected]> Sent: Wednesday, December 31, 1969 7:00 PM Subject: RE: I have to be able to browse the whole database, but it causes corruption Mike, Strikes me you may be looking in the wrong place here i.e at VFP as opposed to the media/Ops system you are storing the tables on. where/what are the tables held on? Dave -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Michael Madigan Sent: 14 May 2012 17:55 To: Pro Fox Email List Subject: I have to be able to browse the whole database, but it causes corruption I have to be able to browse the whole database. If I do it in vfp 9.0, it's been causing corruption. If I use a SQL select, the largest subset a user would use is about 26,000 records from 3 different tables, that takes about 30 seconds. . I was thinking of opening the database again with the noupdate clause, but will that guarantee me no corruption? Can you corrupt an index with a file opened noupdate? --- StripMime Report -- processed MIME parts --- multipart/alternative [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.
