Data Rules Violations
in [Tables]
|
Prev: how do I insert a hyperlink in my access database design?
Next: help transition to access from excel - stevie PIMPS again
From: John Quinn on 8 Mar 2010 13:00 I have a table of 19,000 records with about 225 fields in each record. It is not an indexed table, just a table of educational transactions. Some how when I go to update the historical table seven (7) records have gotten some bad info in them. I know I can copy the table to another database and look at them one field at a time, but this will take forever. Does anyone know a quick method of finding the seven bad records? Thanks in Advance John Q
From: John... Visio MVP on 8 Mar 2010 13:06 "John Quinn" <JohnQuinn(a)discussions.microsoft.com> wrote in message news:B528A571-73CD-4B16-B238-6CB3987701A8(a)microsoft.com... >I have a table of 19,000 records with about 225 fields in each record. It >is > not an indexed table, just a table of educational transactions. > > Some how when I go to update the historical table seven (7) records have > gotten some bad info in them. I know I can copy the table to another > database and look at them one field at a time, but this will take forever. > > Does anyone know a quick method of finding the seven bad records? > > Thanks in Advance > > John Q It depends how you define bad. If you have a criteria, then you can write a query to ientify those "bad" records. John... Visio MVP
From: Steve on 8 Mar 2010 13:32 Hello John, When a table has 225 fields, it is a certainty that your database tables are misdesigned. This is a substantail problem that needs solved. What constitutes a bad record? You can find the seven bad records with an appropriate query. Steve santus(a)penn.com "John Quinn" <JohnQuinn(a)discussions.microsoft.com> wrote in message news:B528A571-73CD-4B16-B238-6CB3987701A8(a)microsoft.com... >I have a table of 19,000 records with about 225 fields in each record. It >is > not an indexed table, just a table of educational transactions. > > Some how when I go to update the historical table seven (7) records have > gotten some bad info in them. I know I can copy the table to another > database and look at them one field at a time, but this will take forever. > > Does anyone know a quick method of finding the seven bad records? > > Thanks in Advance > > John Q >
From: KARL DEWEY on 8 Mar 2010 13:45 >>I have a table of 19,000 records with about 225 fields in each record. It sounds like you have a spreadsheet like Excel instead of a relational database that is the intended purpose of Access. If your data was 'normalized' then it might be easier to find something. -- Build a little, test a little. "John Quinn" wrote: > I have a table of 19,000 records with about 225 fields in each record. It is > not an indexed table, just a table of educational transactions. > > Some how when I go to update the historical table seven (7) records have > gotten some bad info in them. I know I can copy the table to another > database and look at them one field at a time, but this will take forever. > > Does anyone know a quick method of finding the seven bad records? > > Thanks in Advance > > John Q >
From: Jeff Boyce on 8 Mar 2010 14:20
John What "historical table"? If it truly is historical info only, why are you "updating" it? How do you know that there are 7? Do you know which field(s) contain the bad info? Does "bad" = corrupted, or does "bad" = inaccurate? More info, please... Regards Jeff Boyce Microsoft Access MVP -- Disclaimer: This author may have received products and services mentioned in this post. Mention and/or description of a product or service herein does not constitute endorsement thereof. Any code or pseudocode included in this post is offered "as is", with no guarantee as to suitability. You can thank the FTC of the USA for making this disclaimer possible/necessary. "John Quinn" <JohnQuinn(a)discussions.microsoft.com> wrote in message news:B528A571-73CD-4B16-B238-6CB3987701A8(a)microsoft.com... >I have a table of 19,000 records with about 225 fields in each record. It >is > not an indexed table, just a table of educational transactions. > > Some how when I go to update the historical table seven (7) records have > gotten some bad info in them. I know I can copy the table to another > database and look at them one field at a time, but this will take forever. > > Does anyone know a quick method of finding the seven bad records? > > Thanks in Advance > > John Q > |