Data "jumbling"?

[Database Diva]

I have a form to capture data about rental properties - each record has it's
own Autonumber ID and also an administrative code which is alpha-numeric.
This alpha numeric field is integral to the relationships between the various
tables. My client has advised me that this field is not appearing correctly
in certain reports. In the form being used for data entry the property
profile admin number is correct, however in the report is reflecting another
property profile admin number. My copy of the database is fine and the data
is all OK. Any ideas about what could be causing the data to "jumble".

 

[Jerry Whittle]

Worse case it could be a corrupt database file.

It could also be a mistake in the programming of the database where a query,
form, or report is grabbing the data incorrectly.

If you didn't define the table relationships in the Relationships Window and
enable Referiental Integrity, all bets are off.

Did you use lookups at table level? They are evil and can cause data to look
"wrong" even if it's right.

Then there is the plain old users typed in things wrong.

 

[Database Diva]

Dear Jerry

I was concerned about the fact that the data entry form has a drop down list
of the admin number field [alpha numeric numbers] and this can be changed
inadvertantly by users. However when I locked this field in the form design I
found that filtering could not be done on this field and they do need to use
this field to find a specific property by the admin number field when
filtering records.

I have referential integrity and the Admin field is my relational join field
for most of the objects in the database. The property profile table does
have a lookup to select the admin number which gets given by the financial
director and then entered into an Add new Admin Number form. This number then
can be selected from the drop down list in the creation of a new property
profile. If this is the problem - what would you suggest I do?

Also if the data appears correct in the form which is referencing the table
but not in the report which is referencing a query wouldn't this indicate
that the problem is in the data result from the query? I have no problems
with the data in my query here and they are on another continent so I can't
access their query to ascertain whether it has run correctly. The users are
not of a level to do this themselves.

Thanks!

 

[Jerry Whittle]

they are on another continent

Does the report's query have anything to do with currency, date/time or
anything else that can be affected by regional settings. For example I once
had a problem with a query because a country used commas instead of decimals
in numbers. Then there's the whole dd/mm/yyyy vs mm/dd/yyyy thing for dates.
--
Jerry Whittle, Microsoft Access MVP
Light. Strong. Cheap. Pick two. Keith Bontrager - Bicycle Builder.

Dear Jerry

I was concerned about the fact that the data entry form has a drop down list
of the admin number field [alpha numeric numbers] and this can be changed
inadvertantly by users. However when I locked this field in the form design I
found that filtering could not be done on this field and they do need to use
this field to find a specific property by the admin number field when
filtering records.

I have referential integrity and the Admin field is my relational join field
for most of the objects in the database. The property profile table does
have a lookup to select the admin number which gets given by the financial
director and then entered into an Add new Admin Number form. This number then
can be selected from the drop down list in the creation of a new property
profile. If this is the problem - what would you suggest I do?

Also if the data appears correct in the form which is referencing the table
but not in the report which is referencing a query wouldn't this indicate
that the problem is in the data result from the query? I have no problems
with the data in my query here and they are on another continent so I can't
access their query to ascertain whether it has run correctly. The users are
not of a level to do this themselves.

Thanks!

Worse case it could be a corrupt database file.

It could also be a mistake in the programming of the database where a query,
form, or report is grabbing the data incorrectly.

If you didn't define the table relationships in the Relationships Window and
enable Referiental Integrity, all bets are off.

Did you use lookups at table level? They are evil and can cause data to look
"wrong" even if it's right.

Then there is the plain old users typed in things wrong.