John,

From your description here, your application is not so tough (complex maybe
and requiring many tables). What makes your application problematic is the
table with 225 fields. When you run the append query, something is highly
likely to go wrong at some point in time due to the complexity of the data
in the 225 field table. Your tables need to be normalized. What you will
probably end up with are a set of less than fifty tables where all tables
are less than ten fields.

Based on your description here, you have students who progress through
grades 1 to 12 and some may go on to college. In each grade they take
certain subjects. In each subject in each grade they do homework and take
tests. The students are given grades for their homework and tests.
Apparently there is some review and approval process. Comparison of grades
when the student goes into the next level of
education is a simple query or series of queries. The data returned by any
query can be displayed on the screen in a form or printed out in a report.

You say when a problem occurs you eventually find out where the problem is,
but it takes so long. There's a very strong possibility that a well designed
set of tables would eliminate the problem you are seeing. Even if it doesn't
totally eliminate the problem, when a problem occurred, it would take far
less time to find where the problem is.

Steve





"John Quinn" wrote in message
...
It is a sequence of information and approvals for each subject, grade,
homework and tests.

If a student is taking English then we need to show all scorces given and
the relationship to the previous grad or score. With each entry you must
always carrt fields of data for who reviewed it, approved it, made
suggestions or rejected the educational technique used. There is also a
comparison made to grades when the student goes into the next level of
education. For example from grade school to middles school, from middle
school to junior high and from junior high to college.

We even have to know that the student entered college and if that student
graduated or not.

The designers at Fort Hood, indicated iot was the toughest applications
they
have ever seen. Microsoft consultants were amazed at what the attorney's
in
Washington DC want us to keep an accounting of.

The bad data message comes from an append query. The tables are suppose
to
be identical but for some reason this happens once in a while. I
eventually
find out where the problem is, but it takes so long.

Thanks for the interest.

John Q.

"J_Goddard via AccessMonster.com" wrote:

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

.