Help!

[jckcrtr]

I have a table in Access with just under 40,000 customer records (phone number,customer,product,post code,date last called), each day a different post code is printed off and these people are called. The data is printed in reports made from a query which I use to find the records within a certain post code. After the records for the day are printed I delete them by pressing shift and selecting them all then right clicking so when we go back to the post code the same people won't be called again.

However employees have been complaining they are getting back people they've rang either the day before or the day previously, after looking at the sheets (one printed 2 days ago and one printed today) that all the way down every record is identical apart from the fact on one sheet the date's will be in the format "27/11/02" and then on another they'll be in the format "27.11.02". I have no idea whats going on here help!
:banghead:

 

[Rx_]

Please change your title to be more descriptive for your question.

Suggest you create a new column that is named Archive one text character wide Default is "A"
After printing them, run an Update Query to change the "A" (active) to "I" inactive
Create a Make Table Query based on the filter "I" to write to a new table based on the Year+Mo+Date.
Finally, create a Delete Query based on the filter "I"

Lets say that ten records were not reached - They can be changed back to "A" so they stay on the list to be called the following day. Adding the extra column is optional. Keeping a copy is optional. You can just create a Delete query if it suits you.

Manually deleting as you describe may not force the record to the last record. While it should work, there are many reasons why the process could be interrupted.
Using a Query (update, make-table, Delete) will always work.
It is also useful to add a Record Count to display the before and after.

You can search this site for many examples of adding these queries to a button.
The short answer is, write and use action queries.

 

[The_Doc_Man]

The date format change is suspicious. It appears as though you have competing events that use different criteria and that date is text, not actually a date. Otherwise you wouldn't be able to mix them. That might be part of your problem.

Just as a thought: When working with dates, I have always found it is easier to store the date as such and convert it text via a query and Format() function when I really needed text. Not only that, but in the general case, a date field takes LESS space than a text-form date field... 8 bytes for the date/time binary field vs. 10 bytes for dates in xx-xx-xxxx format. Admittedly, it does take a minor paradigm shift if you are more comfortable using text dates, but in the long run it is easier and a bunch more reliable.

 

[jckcrtr]

Thanks for replying guys, I'll be taking on board your advice Rx_ and will remember to use a more descriptive title next time.