In Razzaks great examples he has an end-of-day-routine that you might want to include. Plus you could put a notification script in there in case of errors. Then you would know prior/about the time they figure it out.
Paul From: [email protected] [mailto:[email protected]] On Behalf Of MDRD Sent: Tuesday, August 24, 2010 10:49 AM To: RBASE-L Mailing List Subject: [RBASE-L] - RE: Strange error Paul I never tried, I just added a Delete Rows where custnum Not Exists.... to their end of the day routine, which cleans this junk up. Maybe I will have them send me the files and play with them next time, Thanks Marc From: Paul InterlockInfo <mailto:[email protected]> Sent: Tuesday, August 24, 2010 9:05 AM To: RBASE-L Mailing List <mailto:[email protected]> Subject: [RBASE-L] - RE: Strange error What happens after you backup the db (check the row count of those effected tables) and Pack the db? I compare them side by side afterwards to see (my personal approach-dual monitor). Sincerely, Paul D From: [email protected] [mailto:[email protected]] On Behalf Of MDRD Sent: Tuesday, August 24, 2010 9:07 AM To: RBASE-L Mailing List Subject: [RBASE-L] - Strange error Hi This is the second office with a similar strange problem. About once very 3-4 wks they get some strange data saved in our daily transaction table. One iffice kept getting a charge for Custnum 0 which did not exist in the Customer table, another one got custnum 5897473 and they do not have that custnum. We have PK's and FK's and you can not save a row of data without entering a valid custnum. Also most of the other columns have strange data, like dates of 1899, #$%^ in some fields, currency numbers that look like the deficit and so on. I figure this is some static / junk data coming from the network and getting stuck in the daily trans table or ???? I still wonder how it got saved in the first place or was the data valid at one point then somehow it gets changes? I know the user can not do this and save the row because of the PK / Fk's. Any thoughts? thanks Marc
