dbTalk Databases Forums  

Cross-Checking for Nulls

comp.databases.ms-access comp.databases.ms-access


Discuss Cross-Checking for Nulls in the comp.databases.ms-access forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
croy
 
Posts: n/a

Default Cross-Checking for Nulls - 12-22-2011 , 12:56 PM






MS Access 2002 on Windows XP...

I've been assigned to a database where data-entry is done
twice, and then it is to be "cross-checked" for data that
doesn't match, indicating probable data-entry errors.

Is this even possible? It seems to me that there has to be
some unique-data field that can be used to "align" the two
data-entry tables, then check the rest of the fields.

But even that strategy has me fumbling. If a given field in
tbla has data entered, but it got skipped in tblb, it's
difficult to compare between the two (nulls don't compare).

The goal would be to have a form that will find each
mis-matched pair and display the two records one above the
other, so that a visual glance will easily pick up any
fields that don't match, and the data can be edited right
there. But using any "IIf" statements in the queries
feeding the form cause a non-updatable recordset. Some of
the fields are text fields, and I can get around the problem
by making the default value a zero-length string, which
compares easily. But other fields are numeric, and I can't
figure out how to compare these fields and still come up
with an updatable recordset.

Comments welcome!

--
croy

Reply With Quote
  #2  
Old   
Patrick Finucane
 
Posts: n/a

Default Re: Cross-Checking for Nulls - 12-22-2011 , 07:27 PM






On Dec 22, 12:56*pm, croy <c... (AT) invalid (DOT) net> wrote:
Quote:
MS Access 2002 on Windows XP...

I've been assigned to a database where data-entry is done
twice, and then it is to be "cross-checked" for data that
doesn't match, indicating probable data-entry errors.

Is this even possible? *It seems to me that there has to be
some unique-data field that can be used to "align" the two
data-entry tables, then check the rest of the fields.

But even that strategy has me fumbling. *If a given field in
tbla has data entered, but it got skipped in tblb, it's
difficult to compare between the two (nulls don't compare).

The goal would be to have a form that will find each
mis-matched pair and display the two records one above the
other, so that a visual glance will easily pick up any
fields that don't match, and the data can be edited right
there. *But using any "IIf" statements in the queries
feeding the form cause a non-updatable recordset. *Some of
the fields are text fields, and I can get around the problem
by making the default value a zero-length string, which
compares easily. *But other fields are numeric, and I can't
figure out how to compare these fields and still come up
with an updatable recordset.

Comments welcome!

--
croy
I would look at the query builder. Learn to design queries. Look in
help on how to create totals queries, using the Distinct clause found
in the property sheet of the query builder, and how to create
expressions in the query builder.

Reply With Quote
Reply




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 On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.