Recent content by plog

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

I now remember (and reviewed) your prior post about this new owner and what you are giving him. If I were him, I'd want a working system, lumps and all. Not only are you trying to change tires on a moving car, you're trying to switch drivers while doing so. I'd give the new owner a working...

What happened in the last 6 hours? You started this thread with one table (tblService) with 16 fields and now you've laid out a 49 table database that tracks everything? What's the real story here? Had a guy build a comprehensive database a few years back, he left and now you're the guy stuck...

First, read up on normalization: https://en.wikipedia.org/wiki/Database_normalization That's the process of setting up tables and fields properly. Then google a few tutorials and work thru them. Next, apply what you learn to your data and set up what you think is the correct tables/fields...

No, you were testing for the existence of a record, you didn't look up anything you didn't already know. Further, if you have two records with the same LDOW value the form would open to just one of them.

What's the point of that code? Your querying for the exact value you already have.

You may have missed my quote marks: My advice stands, but keep trying.