So..................
Let's start with some good advice, based upon years of experience, and offered to grant yourself and otherss some sanity when reviewing your code.
Just based off your code, I have no idea what
[REJECT AREA],
[Reject Code Name],
[Reject tags] and
[Purchased Component?] represent. This is the first challenge with trying to figure out your code. We'll come back to this in a moment.
In a previous post, you stated:
Combo Name=RejectAreaCodeID
Yes/No Box Name=Purchased Component?
Form record source Name=QRY-NewTag
This is not helpful for either sets of information you have provided, as the only consistent element between the two is
Purchased Component?, which apparently is a Check Box?
So, here is the advice part (you will hear me telling all folks on this forum the same thing): find a good naming convention for your database objects and use it for every object in your database. At least you have made an attempt at that for your Query Name.
For example, I have no idea what the name of your Form is. But if you had a form named
frmComponents, then
you and
I can automatically make some general assumptions about things without needing additional information. First, we know that we are talking about a Form object--this is helpful, because we know what forms do and how they work. Second, we also have an idea that this Form deals with Components. Now, greater detail might be required to help us understand what aspect of Components this Form deals with, but it gets us headed in the right direction before we even start troubleshooting.
So, here is brief naming convention that might get you started:
frm - Forms
rpt - Reports
cbo - Combo Box
txt - Text Box
chk - Check Box
lbl - Label
qry - Query
tbl - Table
cmd - Command Button
If you search for Database Naming Conventions, you will find plenty to choose from. Just pick one and stick with it. It will save you (and especially others) many headaches.
Second, try (at all costs) to avoid spaces and special characters in your naming convention. Having a Question mark may be an acceptable character in MS Access's system, but it is not wise, as the question mark may also be a wildcard. This can cause problems down the road. Avoiding spaces makes it easier to refer to things in VBA (especially when working with Field Names within recordsets).
Now, based upon the code you provided, it is
literally impossible for me to troubleshoot.
However, I ask you to make some changes to your naming convention and then update your code to reflect those naming changes and repost those changes. I'll be glad to take a look once things make more sense.
Thanks.
221
