I used to use the netgear prosafe gigabit switches and my database would get corrupt from time to time. It happened enough that I had a routine documented and in place when it happened. I switched to more expensive 3com gigabits switches and no more problems(knock on wood). Pay now or pay later... Dan Goldberg
_____ From: [email protected] [mailto:[email protected]] On Behalf Of Paul InterlockInfo Sent: Wednesday, June 24, 2009 10:52 AM To: RBASE-L Mailing List Subject: [RBASE-L] - RE: Pack Index and RB3 file size. This is RWeb ? ('I've been able to fix this with other users on-line' If not, are you dropping packets? Etc.. Assuming this is 7.6 or V-8 and causing this to happen. I know I finally gave in a purchased a new Cisco switch and A LOT of problems went away network wise. ;} A bit of money 10/100/1000 and it seems to go up by users and then it doubles on its way up. Bell curve! Sincerely, Paul From: [email protected] [mailto:[email protected]] On Behalf Of Lawrence Lustig Sent: Wednesday, June 24, 2009 1:22 PM To: RBASE-L Mailing List Subject: [RBASE-L] - Pack Index and RB3 file size. Hi all. I have an application in which I'm getting occasional weirdness in the indexes for one particular table, leading to incorrect results on some queries. I've been able to fix this with other users on-line by using the PACK INDEX <IndexName>. It's a big help to be able to do this with users in the system. Unfortunately, that only helps me AFTER the users have experienced and noticed the problem. I'm thinking of implementing an automatic PACK INDEX routine to run at night to catch these things in advance. This database runs 24 hours, but it's less busy at night. My only concern is that by rebuiling these indexes repeatedly, my #3 file will grow in size. Does anyone have experience with this? Is that what happens? Or does R:Base somehow recycle the space currently used by an index? -- Larry
