Thanks Emmitt
I never thought of this..... it has only happened 3-4 times in 10 years with over a hundred offices running my app so I just chalked it up to a fluke INSERT INTO historytable SELECT * FROM dailytable WHERE keyvalue NOT IN (SELECT keyvalue FROM historytable) DELETE ROWS FROM dailytable WHERE keyvalue IN (SELECT keyvalue FROM historytable) Marc From: Emmitt Dove Sent: Tuesday, December 21, 2010 1:14 PM To: RBASE-L Mailing List Subject: [RBASE-L] - RE: Win 7 and 7.6 1) 99 percent of the time in our case, corrupt data is the result of a lost network connection while a transaction was in progress. But it happens very infrequently, I believe in part because we almost never directly edit the table data. Rather, we use a form and variables, execute code to validate the data, then post the edits to the table with one brief transaction. This also avoids row and table locks as much as possible. It is more work to create/program, but very reliable in a multi-user environment that may have 50 simultaneous connections. 2) A dropped session as a result of a network issue will leave a phantom connection. One way to clean this up is to have the admin connect (bypassing the startup because a phantom connection exist), immediately exit the application and start it again. The phantom connection should be gone. Sometimes it takes a single user connection to clear the phantom connection. We see this a lot - R:BASE may report dozens of connections when only a handful of people are connected. (7.6) 3) No clear reason is forthcoming, but a suggestion that you revisit your logic and decide if you are handling the historical archiving in the most reliable way. For instance, if you're going to copy all the rows in the daily table to the history table, do you first check to see if the rows in the daily exist in the history? Easy to do: INSERT INTO historytable SELECT * FROM dailytable WHERE keyvalue NOT IN (SELECT keyvalue FROM historytable) DELETE ROWS FROM dailytable WHERE keyvalue IN (SELECT keyvalue FROM historytable) You will not create duplicate rows no matter how many times a day this is executed. Emmitt Dove Converting Systems Architect Evergreen Packaging, Inc. [email protected] (203) 214-5683 m (203) 643-8022 o (203) 643-8086 f [email protected] From: [email protected] [mailto:[email protected]] On Behalf Of MDRD Sent: Tuesday, December 21, 2010 13:33 To: RBASE-L Mailing List Subject: [RBASE-L] - RE: Win 7 and 7.6 There are 3 problems 1) one office has corrupt data but they have a new staff person and we wonder if they are the problem. I am not sure how they can corrupt the date unless they are turning off the computer while connected. 2) We have a start up routine that checks the number of users connected to the DB, if another user is connected skip the Autocheck routine that also makes a copy of the *.RB* files. This happened to the tech when no one else was connected to the db, so he was wondering if anything in Win 7 could make it look like something was connected to the data files. I told him my best guess was AV, then he said it is not scanning our folder / files. 3) We keep daily transactions in a daily table, print the end of day report then Close the day which copies the rows to the History table then deletes the rows in the Daily table. One day last week they had duplicates of everything on that day, like they Closed the day, the rows were copied to the History, but no rows were deleted, then they tried to run the Close day routine again. Thanks Marc From: Emmitt Dove Sent: Tuesday, December 21, 2010 12:13 PM To: RBASE-L Mailing List Subject: [RBASE-L] - RE: Win 7 and 7.6 Then I must have misunderstood the issue. What is the issue? Emmitt Dove Converting Systems Architect Evergreen Packaging, Inc. [email protected] (203) 214-5683 m (203) 643-8022 o (203) 643-8086 f [email protected] From: [email protected] [mailto:[email protected]] On Behalf Of MDRD Sent: Tuesday, December 21, 2010 12:36 To: RBASE-L Mailing List Subject: [RBASE-L] - RE: Win 7 and 7.6 Emmitt I agree, their tech said he specifically excluded our folder and files from the scans. Thanks Marc From: Emmitt Dove Sent: Tuesday, December 21, 2010 11:14 AM To: RBASE-L Mailing List Subject: [RBASE-L] - RE: Win 7 and 7.6 Why would anyone want the database and related files scanned anyway? I worked hard to assure that in our company anything related to our database and the code that drives it is specifically excluded from virus scanners, especially any on-access scans. That would impose a terrific overhead on file access that accomplished nothing because the source of all our files is internal. Emmitt Dove Converting Systems Architect Evergreen Packaging, Inc. [email protected] (203) 214-5683 m (203) 643-8022 o (203) 643-8086 f [email protected] From: [email protected] [mailto:[email protected]] On Behalf Of MDRD Sent: Tuesday, December 21, 2010 12:10 To: RBASE-L Mailing List Subject: [RBASE-L] - Win 7 and 7.6 Hi Is there any known issues with RBase 7.6 compiled app on Windows 7 64bit systems? I am sure the simple answer is no but I was wondering about caching or some other Win 7 features that could cause a problem. I just got a call from a computer tech that does the support for 2 of our offices and both offices have problems. They have used RBase for years but just recently got new computers with Win 7 on them and that is why they asked me to double check. They are using Windows Essentials and the scans are not scanning our DB folder or RBase files. Thanks Marc
