OMGosh! Even Intuit admits packet information will corrupt its db.
I am sure a lot of people are going to chime in here but I thought of this example first. ONLY because year's back I had a problem with some named db engine that I could not get into that would corrupt and RBase was not. Even with the packet failures. Luck of the draw and a few temp tables J That's what I liked about RBase and all along (over 22 years now) it is more stable. If I find the article (if needed after others chime in)I will forward examples and I think I would cc them to the CEO and IT person. Then perhaps they can find the packet that is corrupt in his IT pocket. (Joking but .. give me a break) Sincerely, Paul D No more comments -- I am restaining myself! From: [email protected] [mailto:[email protected]] On Behalf Of MDRD Sent: Thursday, August 19, 2010 1:06 PM To: RBASE-L Mailing List Subject: [RBASE-L] - Corrupt DB Hi I have this one user that keeps getting corruption in this one table. For the most part this is the only office having a problem. They have a computer tech that is some hot shot MS certified network something or other and I am over my head in discussing what may be causing the problem. As luck would have it this office has a lot of influence with my other users so I really need to nail this down. They were able to add 1,100 rows of data since the last corruption, so I told the tech that I do not think it is RBase or my app also they are basically the only office having a problem. I suggested some kind of junk data in one of the rows and everytime they hit that row of data or that customer it corrupts the DB but I am only grabbing at straws. He sent me this... so how should I respond? I can find tons of links about Access corruption due to network issues, but is he talking about a CS db compared to file server db? >From a network standpoint, it cannot corrupt the database. The packets could get corrupted, but then you'd have to ask why the program you use as the engine for PS (this my app), then commits a corrupt packet of data...their engine is the only thing that can modify the file. That is what I'm getting at here...only they and the local hardware/3rd party software can modify that dbase on the local machine. Or do they allow that other workstation to make direct edits over the network? That would be crazy... Again, yes, the local hardware and third party software can indeed cause corruption to the physical file, but I would highly doubt it would happen at the same place/table of a Db each and every time. That is one if the things that says software/process about this. Can you tell me how their flow goes? How they edit from a client etc? I need to understand how the Db engine works. That will help whether it's software or hardware...it will tell us where and when to look. thanks for any help Marc
