Search results

Think we need more specifics. I have two hunches based on nothing you've said, just experience here: 1. Your math could be more efficient. 30 fields based on 15 inputs is a lot, and then you say that some calculations feed into other calculations downstream. Perhaps some of those...

You're printing out a value on the form, not a value from the record set.

"R915" doesn't look like a number to me. Are you using base 28 or more? In a table, you should store your values with the data type they need to be. If you will be doing math on data then you should store them as numbers. That means the "915" part goes into a field by itself as a number, and...

You can't have it both ways. Either you get a list of unique artists because the artist names are distinct. Or you get duplicate artist names because record_id/artist name is not distinct to artist.

Is 'artist_name' a field in qryRecord_Search_Form_record2? My guess is no, it's that horrible one with a slash and space in it.

Agree with MajP and my guess as to where it is going wrong is that you are counting gifts, not donors. [PY Gifts] is most likely a list of gifts which means if a donor gave multiple gifts they are showing up multiple times in that table and you are counting them each time they gave a gift...

With those database constraints I was wrong. Cheeky's solution will work. Sorry.

Fails if 2 bike/car records and no bike/car records. False positive. Fails if a bike record and a car record and then matching records (bike bike car, car car bike, car car bike bike). False negative.

Is your number 2 in response to my #2? If so you missed the point. Reread my explanation. tblCategoryTypes is a subset of tbl_ContactCategories. Every field in tblCategoryTypes is in tbl_ContactCategories. That's wrong.

Not that simple actually--but not too hard. Gonna take a subquery. There's a few ways to do this so I'm betting this turns into another pedantic coding contest. Here's my entry: SELECT ContactID, MAX([Category Type]) AS Type1, MAX([Category Type]) AS Type2 FROM tbl_Contact_Category WHERE...

The +1 needs to go to the interval not the dateofinspection.

Definitely. I mean your solution to fallible employees is relying on those fallible employees. And you don't need to, you can catch these errors with the system itself. I'd let them clock out and notify them via a message box that they need to contact an admin to fix it. Further, I'd have...

So why harass users with a kludge fix that is ultimately pointless? If they forget to login, can't this be resolved without them further engaging with that form? If a manual adjustment is necessary, why make them do something with the form? What exactly is going to occur in that manual...

Programming 101: Divide, isolate and conquer You have 2 function calls on the line you think it is failing on. Format() and DMax(). Does the DMax() work by itself? Does the Format() work if you hardcode a value into it? Both of them take multiple arguments. When you find which function...

The devil is in the edges. The most granular calendar unit is the day--every other unit can be expressed in days...but not consistently. Months come with 28,29,30 & 31 days. Years come with 365 & 366 days. Exactly where and how do you want to draw your line? Born July 1. Today is August 31...

Subform(s). https://support.microsoft.com/en-us/office/create-a-form-that-contains-a-subform-a-one-to-many-form-ddf3822f-8aba-49cb-831a-1e74d6f5f06b You remove the combo boxes for those 4 things and either make 1 subform for that entire table I described or make 4 subforms--1 for each...

If that's truly the case, then storing loyalty amount in both places is actually fine. Did you write that VBA code that does the INSERT? Because the simplest way is modify that to get the LoyaltyAmount from the Members table and include it in there. Either with a Dlookup or by modifying the...

I think you need to ditch the multi value fields and fix your structure. Before I get into that, don't use spaces in table/field names. It's going to make coding/querying difficult later on. Use underscores (Like_This) or camelcase (LikeThis). In the database you posted you have a main...

Sort of easy, but not the right way to do things. You don't store data in more than one place in a database. Can the Loyalty amount of a customer change? If so, do you want to record those changes or do not care what a customers loyalty amount was 3 weeks/months/years ago?

You don't have a database you have a spreadsheet. Use Excel and this issue goes away. If you want to use Access I suggest you normalize your data (that's the process of properly structuring your tables/fields): https://en.wikipedia.org/wiki/Database_normalization