Corruption or design flaw?

Hi all



I have a database in Access 2003 (2002-2003 file format).

There is a form that updates a query table.

On certain records, updating the entry for one particular field on the form
does NOT reflect in the relevant field being updated in the query table. On
those records where this effect is observed, it happens every time however
many times I attempt to alter the field via the form.



It occurs to me that there are two possible explanations for this
undesirable behaviour:

(1) Design flaw (most likely explanation), or

(2) Data corruption



I wish to eliminate data corruption as a cause, before I spend time hunting
for a design flaw. Is there a procedure for doing this (and identifying
corrupt records)? Should I assume that the possibility of data corruption
is so vanishingly unlikely that it is not worth considering?



I have been through the Tools/Compact and Repair option already.




Thanks


--
Return email address is not as DEEP as it appears

Belay that - problem solved. Sorry to have troubled you

"Jack Sheet" wrote in message
...
Hi all



I have a database in Access 2003 (2002-2003 file format).

There is a form that updates a query table.

On certain records, updating the entry for one particular field on the
form does NOT reflect in the relevant field being updated in the query
table. On those records where this effect is observed, it happens every
time however many times I attempt to alter the field via the form.



It occurs to me that there are two possible explanations for this
undesirable behaviour:

(1) Design flaw (most likely explanation), or

(2) Data corruption



I wish to eliminate data corruption as a cause, before I spend time
hunting for a design flaw. Is there a procedure for doing this (and
identifying corrupt records)? Should I assume that the possibility of
data corruption is so vanishingly unlikely that it is not worth
considering?



I have been through the Tools/Compact and Repair option already.




Thanks


--
Return email address is not as DEEP as it appears

It would be nice if you shared with us what the resolution was. There may be
others that could benefit from what you have done.

"Jack Sheet" wrote:

Belay that - problem solved. Sorry to have troubled you

"Jack Sheet" wrote in message
...
Hi all



I have a database in Access 2003 (2002-2003 file format).

There is a form that updates a query table.

On certain records, updating the entry for one particular field on the
form does NOT reflect in the relevant field being updated in the query
table. On those records where this effect is observed, it happens every
time however many times I attempt to alter the field via the form.



It occurs to me that there are two possible explanations for this
undesirable behaviour:

(1) Design flaw (most likely explanation), or

(2) Data corruption



I wish to eliminate data corruption as a cause, before I spend time
hunting for a design flaw. Is there a procedure for doing this (and
identifying corrupt records)? Should I assume that the possibility of
data corruption is so vanishingly unlikely that it is not worth
considering?



I have been through the Tools/Compact and Repair option already.




Thanks


--
Return email address is not as DEEP as it appears

On Tue, 5 Sep 2006 12:17:19 +0100, "Jack Sheet"
wrote:

There is a form that updates a query table.

Just bear in mind - there is NO SUCH THING as a "query table".

Data is stored in Tables, and only in Tables.

Data can be combined, filtered, and sorted using Queries - but a Query
is *not* a table, and the data in a query has no independent
existance; it depends 100% on the underlying Tables.

John W. Vinson[MVP]

Yea. Even if it's embarrasing. Like the time I spent over 2 hours
troubleshooting a car that wouldn't start only to find that it was out of
gas......

Or in Access when I made a complete fool out of myself in front of a college
class trying to show them how to use Excel to update an Access table and it
wouldn't work. Little did I know that MS removed that functionality due to a
patent infringement case during a recent service pack.
--
Jerry Whittle
Light. Strong. Cheap. Pick two. Keith Bontrager - Bicycle Builder.


"Klatuu" wrote:

It would be nice if you shared with us what the resolution was. There may be
others that could benefit from what you have done.

"Jack Sheet" wrote:

Belay that - problem solved. Sorry to have troubled you

"Jack Sheet" wrote in message
...
Hi all



I have a database in Access 2003 (2002-2003 file format).

There is a form that updates a query table.

On certain records, updating the entry for one particular field on the
form does NOT reflect in the relevant field being updated in the query
table. On those records where this effect is observed, it happens every
time however many times I attempt to alter the field via the form.



It occurs to me that there are two possible explanations for this
undesirable behaviour:

(1) Design flaw (most likely explanation), or

(2) Data corruption



I wish to eliminate data corruption as a cause, before I spend time
hunting for a design flaw. Is there a procedure for doing this (and
identifying corrupt records)? Should I assume that the possibility of
data corruption is so vanishingly unlikely that it is not worth
considering?



I have been through the Tools/Compact and Repair option already.




Thanks


--
Return email address is not as DEEP as it appears

Thanks, John - sloppy. Will do better

"John Vinson" wrote in message
...
On Tue, 5 Sep 2006 12:17:19 +0100, "Jack Sheet"
wrote:

There is a form that updates a query table.

Just bear in mind - there is NO SUCH THING as a "query table".

Data is stored in Tables, and only in Tables.

Data can be combined, filtered, and sorted using Queries - but a Query
is *not* a table, and the data in a query has no independent
existance; it depends 100% on the underlying Tables.

John W. Vinson[MVP]

Embarrassing to me? certainly. Helpful to others? I doubt it, but you can
judge.

Some eejit had created (in error) some duplicate records in the table
without my knowledge. The record that I THOUGHT that I was updating via the
form was the duplicate record. The report that I was using to check the
progress (correctly) filtered out the (now amended) duplicate record, but
left the original (unedited) record displayed.

"Klatuu" wrote in message
...
It would be nice if you shared with us what the resolution was. There may
be
others that could benefit from what you have done.

"Jack Sheet" wrote:

Belay that - problem solved. Sorry to have troubled you

"Jack Sheet" wrote in message
...
Hi all



I have a database in Access 2003 (2002-2003 file format).

There is a form that updates a query table.

On certain records, updating the entry for one particular field on the
form does NOT reflect in the relevant field being updated in the query
table. On those records where this effect is observed, it happens
every
time however many times I attempt to alter the field via the form.



It occurs to me that there are two possible explanations for this
undesirable behaviour:

(1) Design flaw (most likely explanation), or

(2) Data corruption



I wish to eliminate data corruption as a cause, before I spend time
hunting for a design flaw. Is there a procedure for doing this (and
identifying corrupt records)? Should I assume that the possibility of
data corruption is so vanishingly unlikely that it is not worth
considering?



I have been through the Tools/Compact and Repair option already.




Thanks


--
Return email address is not as DEEP as it appears

Jerry Whittle wrote:
Yea. Even if it's embarrasing. Like the time I spent over 2 hours
troubleshooting a car that wouldn't start only to find that it was out of
gas......

snip
Don't feel too bad I had a similar incident only in my case the
car wasn't in park :-)

gls858