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



.