|
||||||
WelcomeWelcome! Track Partial Invoice PaymentsWelcome to Microsoft Access Developer Level 7. In this course we will focus on handling partial payments in your order entry system, including building a payment form, tracking the history of payments on invoices, and displaying the total payments and amount due on your main order form and printable invoices. We will also discuss features like handling unpaid invoices, quotations, and using different icons in message boxes with VBA. You should have completed the previous Developer Level 6 class, as well as the Beginner, Expert, and Advanced series for best results. Sample databases are available for download. NavigationKeywordsAccess Developer, partial payments, order entry system, invoice payments, VBA, payment form, payment tracking, payment history, payment fields, order form, amount due, payment icons, message box icons, quotations, printable invoice, subreport field
More InformationTranscriptWelcome to Microsoft Access Developer Level 7 brought to you by AccessLearningZone.com. I am your instructor, Richard Rost. Today's class is going to cover entering partial payments for the invoices in our order entry system. So far to date, we have a system where you can either mark an invoice paid or not paid. But what happens if you have a $5,000 order and the customer wants to pay $200 now, $500 later? We need a way to track that. So, that is the one major topic for today's class. We are going to cover a whole bunch of different VBAs and some other scenarios, as well as some tips and tricks and things that go along with that. Even if you might not be doing partial payments in your database, all of the stuff I am going to show you can be useful. Remember, Access is like playing with Legos. It is just learning the different pieces, and they all can be put together in a different way. The prerequisite, of course, is that you should have taken the Access Developer Level 6, and of course all of my Beginner and Expert courses, and preferably the Advanced Series classes as well. For those of you who have never taken my classes before, they are broken down into the Beginner, Expert, Advanced, and Developer series, and this is Developer Level 7. The sample databases for my courses can be found here at this address: 599c.com/databases. I do strongly recommend you build the database with me in class from the beginning, but if you have not, if you jumped in the middle somewhere, you can download my copy of the database here. Everything that I cover in today's class should be fine in Microsoft Access 2007 and beyond. I am thinking about it, and it probably will still work even in 2003 and the older versions. All the VBA really has not changed much. And yes, I know that Access is going to be coming out with 2019 pretty soon. I have been looking over the review notes, and I do not think too much is going to change from 2016 to 2019, but of course check my website if you are watching this class in the future, and you will know if there are any changes. Check the website and I will post some notes on the class page. All right, so let us take an in-depth look at what we are covering in today's class. In lesson one, we are going to start working on partial payments. Right now, our invoices can be either paid or unpaid. Sometimes customers will pay only part of an invoice. We want to be able to track the entire history of all the payments on a particular invoice. So, we are going to build a payment form. We are going to build fields on our main order form so we can see the total payments made and the amount due. In lesson two, we are continuing with partial payments. We are going to learn about VB exclamation and some different little icons you can put in your message boxes. We are going to handle situations if the order is paid or if it is a quotation. We will not let the user put payments on it. We are going to add the payments information, including payments made and amount due, on the printable invoice. In lesson three, we are continuing with partial payments. We are going to see how we can make the payments made and the amount due not show up if it is a quotation. We are going to see how we can get a field that is only on the parent report into the subreport. IntroWelcome to Microsoft Access Developer Level 7. In this course we will focus on handling partial payments in your order entry system, including building a payment form, tracking the history of payments on invoices, and displaying the total payments and amount due on your main order form and printable invoices. We will also discuss features like handling unpaid invoices, quotations, and using different icons in message boxes with VBA. You should have completed the previous Developer Level 6 class, as well as the Beginner, Expert, and Advanced series for best results. Sample databases are available for download. QuizQ1. What main feature is being added to the order entry system in this class? A. Ability to process refunds automatically B. Support for entering partial payments on invoices C. Automatic invoice emailing D. Integration with Excel only Q2. Why is it important to be able to track partial payments on invoices? A. To allow customers to pay large invoices in multiple payments B. To send promotional offers to clients C. To increase the order processing speed D. To prevent duplicate payments Q3. What tool or feature is being used to add functionality for partial payments? A. SQL Server Integration Services B. A custom VBA payment form C. Microsoft PowerPoint D. Access Macros only Q4. Where can students download the sample database for this course? A. From a local network share B. 599c.com/databases C. Only from the Microsoft Office website D. It is included within Microsoft Access by default Q5. Which previous courses are recommended before taking Access Developer Level 7? A. Only the Beginner series B. Beginner, Expert, Advanced, and Developer Level 6 C. Any general programming course D. Only Developer Level 1 Q6. What happens currently in the system if a customer pays only part of an invoice? A. The system automatically splits the invoice B. The system cannot record partial payments and considers the invoice unpaid until fully paid C. The system deletes the invoice D. The system sends a warning email Q7. What lesson introduces the way to display the total amount paid and the amount due on the main order form? A. Lesson two B. Lesson three C. Lesson one D. Lesson four Q8. What additional feature is added to the printable invoice in lesson two? A. Company logo B. Payment information such as payments made and amount due C. Customer signature field D. Product barcodes Q9. What programming topic is specifically mentioned in lesson two? A. SQL Transactions B. VBA message boxes with different icons C. C++ pointers D. JavaScript integration Q10. How does Access relate to Legos, according to Richard Rost? A. It requires building with a specific set of instructions B. Once you learn the different pieces, they can be put together in many ways C. You cannot change anything after building D. Each project must be built exactly the same way Q11. For which versions of Access should the material in this course work without issues? A. Only Access 2019 and later B. Access 2007 and newer, possibly even 2003 C. Only Access 2016 D. Only Access Online Q12. What should users check if they are using a newer version of Access in the future? A. The system event log B. The course website for notes and updates C. The printer settings D. The Windows registry file Q13. What happens in lesson three regarding quotations? A. Quotations automatically convert to paid invoices B. Payments made and amount due fields are hidden if it is a quotation C. Quotations must always have a payment entry D. Quotations are deleted after seven days Q14. What is shown regarding reports and subreports in lesson three? A. How to color the background B. How to get a parent report field value into a subreport C. How to generate a CSV export only D. How to print multiple copies automatically Answers: 1-B; 2-A; 3-B; 4-B; 5-B; 6-B; 7-C; 8-B; 9-B; 10-B; 11-B; 12-B; 13-B; 14-B DISCLAIMER: Quiz questions are AI generated. If you find any that are wrong, don't make sense, or aren't related to the video topic at hand, then please post a comment and let me know. Thanks. SummaryToday's video from Access Learning Zone is Microsoft Access Developer Level 7. I am your instructor, Richard Rost. In this course, we focus on how to handle partial payments within our order entry system. Up to this point, our database has only offered a binary option for invoices: either marked as paid or unpaid. However, businesses frequently encounter situations where an invoice remains only partially paid for an extended time. For example, a customer might have a $5,000 order but chooses to pay $200 now and $500 at a later date. We need a method to track each payment as it happens. That is the core topic we will be developing in this class. Throughout this lesson, I will walk you through a range of different VBA techniques, along with several scenarios that frequently arise in real-world databases. Even if you have not had to manage partial payments in your own projects yet, the skills covered today - such as form design, calculating balances, and improving the user experience - will be valuable for many other tasks in Access development. I like to compare Access to working with Legos: it is important to learn how each piece works, and then you are free to fit them together however you need for your unique projects. To get the most out of this class, you should have already completed Access Developer Level 6, as well as all of my Beginner and Expert series. Ideally, you will have finished the Advanced classes too. For anyone who is new to my training, here is how my courses are structured: they start at the Beginner level and proceed through Expert, Advanced, and finally Developer topics. This particular lesson is Developer Level 7. You can download the sample databases used in all my courses at 599c.com/databases. While I recommend building the sample database alongside me from scratch, you also have the option to download my files if you are joining in the middle of the series. Everything we cover today will work with Microsoft Access 2007 and all versions that have followed. Most concepts should still function even in Access 2003 and earlier versions, since the core VBA features have barely changed across editions. With Access 2019 coming out soon, I have checked the review notes and from what I have seen, not much is different between 2016 and 2019 for what we are covering here. However, always check my website, especially if you are viewing this lesson in the future. I post any important updates or differences on the class page. Let me give you an overview of how this class is organized: Lesson one begins with building the framework for handling partial payments. Our goal is to move beyond simply tracking whether invoices are paid. We need to track the full history of all payments tied to every invoice. To achieve this, I will walk you through building a dedicated payment form, along with adding new fields to the main order form to display the total payments received and the outstanding amount due. Lesson two continues with partial payments. We will look into using different message box icons such as VB exclamation to improve user feedback. You will learn how to deal with different situations such as preventing payments from being added to quotations or already fully paid orders. We will also cover how to include payment information - both total payments made and balance due - on printable invoices. In lesson three, we refine the display logic for partial payments. You will see how to ensure payment fields do not appear if the document is merely a quotation. Additionally, I will show you how to make a field from the parent report available inside a subreport, which is a technique you will find useful in many Access reporting scenarios. You can find a complete video tutorial with step-by-step instructions on everything discussed here on my website at the link below. Live long and prosper, my friends. Topic ListEntering partial payments for invoices Tracking payment history on invoices Building a payment form Adding total payments made and amount due fields to the order form Displaying payments information on printable invoices Handling quotations without payments Using message box icons in VBA Hiding payments made and amount due for quotations Displaying parent report fields in subreports Primary Topics
partial payments, invoice payment tracking, order entry system, Access VBA, payment forms, reports, payment history Secondary Topics
message boxes, user interface enhancements, parent-child report data, database version compatibility |
||
|
| |||
| Keywords: Access Developer, partial payments, order entry system, invoice payments, VBA, payment form, payment tracking, payment history, payment fields, order form, amount due, payment icons, message box icons, quotations, printable invoice, subreport field PermaLink How To Track Partial Payments for Invoices and Calculate Amount Due in Microsoft Access |
