Thanks Razzak
Marc
--------------------------------------------------
From: "A. Razzak Memon" <[email protected]>
Sent: Tuesday, August 24, 2010 9:08 AM
To: "RBASE-L Mailing List" <[email protected]>
Subject: [RBASE-L] - Re: Strange error
At 09:06 AM 8/24/2010, Marc Schluter wrote:
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?
Marc,
When was the last time you have performed an actual data
integrity check on each of these database(s) within all of
these remote locations?
Having said that, do yourself and your clients a big favor.
I would take the time to re-evaluate each database at each
location, especially with these frequent issues, and
perform a full data integrity check to essentially re-build
these databases using the latest version/build of the
currently available updates of R:BASE.
http://www.rupdates.com
Once these databases are re-built without any -ERROR-s
(using the latest updates), test everything accordingly
and then deploy your applications to your client sites.
In addition, since you are deploying a compiled application,
make sure that you re-compile the application using the
same version/build of R:BASE and be certain that there
are no old Plugins (.RBLs), .EXEs and DLLs in the path.
These required steps will insure the integrity of your
database and application and will help prevent future
strange errors.
Always carry out due diligence research to avoid these
data integrity mishaps.
There is a technical article regarding "R:BASE Database
Maintenance" that will help you understand the required
steps.
Hope this helps!
Very Best R;egards,
Razzak.
