J
John H W
Last week data on people attending a class was entered for classes on 5/23,
5/24, 5/26 and 5/27. The data is in the table. The query will pull the
records for 5/23, 5/24 and 5/27 (by date), but not for 5/26. The date
"looks" the same in the table, i.e, 5/24/2005, 5/26/2005 (it is formatted as
Short Date). The autonumber (primary key) is sequencial within a date set,
although the data for 5/26 was entered between 5/23 and 5/24.
Recordsets pulled by the same query based on the individual dates are
correct for 5/23, 5/24, & 5/27, but has a recordcount for 5/26 of 0 records
(should be 13). When I run a query for the entire database, it is 17 records
short (5/26 has 13 and 5/27 had 4 records), so whatever is causing a query to
not pull 5/26 is stopping a loading of the table (based on a query which also
pulls the name of the client from another table) of anything later than 5/24.
I have run the repair function, same thing happens.
Any comments or ideas?
John H W
5/24, 5/26 and 5/27. The data is in the table. The query will pull the
records for 5/23, 5/24 and 5/27 (by date), but not for 5/26. The date
"looks" the same in the table, i.e, 5/24/2005, 5/26/2005 (it is formatted as
Short Date). The autonumber (primary key) is sequencial within a date set,
although the data for 5/26 was entered between 5/23 and 5/24.
Recordsets pulled by the same query based on the individual dates are
correct for 5/23, 5/24, & 5/27, but has a recordcount for 5/26 of 0 records
(should be 13). When I run a query for the entire database, it is 17 records
short (5/26 has 13 and 5/27 had 4 records), so whatever is causing a query to
not pull 5/26 is stopping a loading of the table (based on a query which also
pulls the name of the client from another table) of anything later than 5/24.
I have run the repair function, same thing happens.
Any comments or ideas?
John H W