If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
|
Thread Tools | Display Modes |
|
#1
|
|||
|
|||
Data Rules Violations
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 |
#2
|
|||
|
|||
Data Rules Violations
"John Quinn" wrote in message
... 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 |
#3
|
|||
|
|||
Data Rules Violations
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 "John Quinn" wrote in message ... 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 |
#4
|
|||
|
|||
Data Rules Violations
Copying my answers again? Do you ever have an original thought?
John... Visio MVP "Steve" wrote in message ... 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 "John Quinn" wrote in message ... 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 |
#5
|
|||
|
|||
Data Rules Violations
Sorry Staeve;
Every field depends on the previous field. If I designed a table for each scenario, I would have about 200 tables being linked to I do not know how many other tables. Testing applications have become very difficult and are now one of the toughest applications to design. Microsoft consultants were at the Texas headquarters because so many people have had comments like yours. Did could not come up with a better design either. It cost the State of Texas $275,000.00 to do almost exactly what we did. Some applications do not coincide with Microsoft's or IBM rules! Thanks for getting back however! John Q "Steve" wrote: 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 "John Quinn" wrote in message ... 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 . |
#6
|
|||
|
|||
Data Rules Violations
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 |
#7
|
|||
|
|||
Data Rules Violations
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" wrote in message ... 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 |
#8
|
|||
|
|||
Data Rules Violations
The legal community for the Department of Education is now requiring a weekly
account of all the students we test and grade. I move the infor to the SQL database in the event of a law suit by the parents. Thanks for getting back! Hope this gives you an understanding of what we face in education. John Q. "Jeff Boyce" wrote: 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" wrote in message ... 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 . |
#9
|
|||
|
|||
Data Rules Violations
Sorry, I didn't see answers to the questions ... I asked them to get
clarification. 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" wrote in message ... The legal community for the Department of Education is now requiring a weekly account of all the students we test and grade. I move the infor to the SQL database in the event of a law suit by the parents. Thanks for getting back! Hope this gives you an understanding of what we face in education. John Q. "Jeff Boyce" wrote: 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" wrote in message ... 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 . |
#10
|
|||
|
|||
Data Rules Violations
Hi -
How did you determine that 7 records had 'bad' data? Did MS Access give you an error message on a data import, or did you just happen to notice the bad data? If the 'bad' data is actually in the tables, then it is not likely to be a problem with MS Access - more likely to be a problem with the source of the data. As has been pointed out, 225 fields is a REALLY large table - can you give us an idea of what it contains? It might be that there is a much more efficient way of reaching your goal. John 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 -- John Goddard Ottawa, ON Canada jrgoddard at cyberus dot ca Message posted via http://www.accessmonster.com |
|
Thread Tools | |
Display Modes | |
|
|