A Microsoft Office (Excel, Word) forum. OfficeFrustration

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.

Go Back   Home » OfficeFrustration forum » Microsoft Access » Database Design
Site Map Home Register Authors List Search Today's Posts Mark Forums Read  

Data Rules Violations



 
 
Thread Tools Display Modes
  #1  
Old March 8th, 2010, 07:00 PM posted to microsoft.public.access.tablesdbdesign
john quinn
external usenet poster
 
Posts: 18
Default 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  
Old March 8th, 2010, 07:06 PM posted to microsoft.public.access.tablesdbdesign
John... Visio MVP
external usenet poster
 
Posts: 900
Default 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  
Old March 8th, 2010, 07:32 PM posted to microsoft.public.access.tablesdbdesign
Steve[_77_]
external usenet poster
 
Posts: 1,017
Default 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  
Old March 8th, 2010, 07:45 PM posted to microsoft.public.access.tablesdbdesign
KARL DEWEY
external usenet poster
 
Posts: 10,767
Default 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

  #5  
Old March 8th, 2010, 08:20 PM posted to microsoft.public.access.tablesdbdesign
Jeff Boyce
external usenet poster
 
Posts: 8,621
Default 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



  #6  
Old March 8th, 2010, 08: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

  #7  
Old March 8th, 2010, 09:07 PM posted to microsoft.public.access.tablesdbdesign
John... Visio MVP
external usenet poster
 
Posts: 900
Default 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





  #8  
Old March 8th, 2010, 09:51 PM posted to microsoft.public.access.tablesdbdesign
john quinn
external usenet poster
 
Posts: 18
Default 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



.

  #9  
Old March 8th, 2010, 09:53 PM posted to microsoft.public.access.tablesdbdesign
john quinn
external usenet poster
 
Posts: 18
Default 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



.

  #10  
Old March 8th, 2010, 10:03 PM posted to microsoft.public.access.tablesdbdesign
john quinn
external usenet poster
 
Posts: 18
Default Data Rules Violations

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

.

 




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Forum Jump


All times are GMT +1. The time now is 04:31 PM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Copyright ©2004-2024 OfficeFrustration.
The comments are property of their posters.