LimitedTech
Technical User
Background:
I have a Database we have used for 12 years. Access 2003 (Access 2000 file format).
The user opens a form it show open invoices we owe to a customer. It is a continuous form. Only one control is available to the user in the Detail. CheckNum, it corresponds to TxtChkNumber in the table.
In the Form Footer, I have an unbound text box, labeled "Pay on Check Number". The user enters the check number for the invoices they want to pay in the CheckNum box and then in the Unbound text box in the footer.
The user clicks the "PAY" button. The button initiates a macro.
The macro first prints the check and then runs an update query. The query updates a yes/no to yes, updates paiddate to today's date for every record with the check number matching the one entered into the unbound text box.
Question:
Today for some reason (only one time out of several done today) it looks like the check printed but the query did not run. The User claims nothing out of the ordinary happened when she performed the operation. Is this something that happens? As I have mentioned this has been in operation for over 12 years and we haven't had any problems. My gut instinct tells me the user managed to create this anomaly but she is adamant nothing out of the ordinary happened. You can see how this is a huge problem if paid invoices are not updating to paid.
Follow up Question: Does anyone have an idea for a better way to institute this operation?
I have a Database we have used for 12 years. Access 2003 (Access 2000 file format).
The user opens a form it show open invoices we owe to a customer. It is a continuous form. Only one control is available to the user in the Detail. CheckNum, it corresponds to TxtChkNumber in the table.
In the Form Footer, I have an unbound text box, labeled "Pay on Check Number". The user enters the check number for the invoices they want to pay in the CheckNum box and then in the Unbound text box in the footer.
The user clicks the "PAY" button. The button initiates a macro.
The macro first prints the check and then runs an update query. The query updates a yes/no to yes, updates paiddate to today's date for every record with the check number matching the one entered into the unbound text box.
Question:
Today for some reason (only one time out of several done today) it looks like the check printed but the query did not run. The User claims nothing out of the ordinary happened when she performed the operation. Is this something that happens? As I have mentioned this has been in operation for over 12 years and we haven't had any problems. My gut instinct tells me the user managed to create this anomaly but she is adamant nothing out of the ordinary happened. You can see how this is a huge problem if paid invoices are not updating to paid.
Follow up Question: Does anyone have an idea for a better way to institute this operation?