View Single Post
  #6  
Old March 8th, 2010, 07:26 PM posted to microsoft.public.access.tablesdbdesign
J_Goddard via AccessMonster.com
external usenet poster
 
Posts: 221
Default 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