Search results

Whoops! Typo. It actually counts nameXtaskQ which is already filtered by the controls in the parent form. And yes, as I explained, I substituted names for what I am really working on for sake of privacy. I don't think the example is bad--all that mattered for this question was form, not...

Let me ask a mostly unrelated follow-up. If I don't get responses here, I'll pop it into a new thread. I want the user to be able to select at most one default. The way I tried to do this was to use the subform's BeforeUpdate event. Here is the code, more or less (I'm editing it quickly from my...

Wow, nice! The reason it wasn't working for me before was that, if the parent form is unbound, when you click the three-dotted button for linking master-child fields, it gives the error "Can't build a link between unbound forms". But it looks like just typing in the values for these properties...

Oh, if these were actually first and last names in the real database, I would agree. In the actual use case, it makes way more sense, and though there will still be a few "dead combinations", I don't think it is worth designing a form for "full names". Could be wrong, but that's why I'm...

I'm gonna get back to this thread when I'm at work tomorrow, but were you also able to change the first and last names? That was the other problem.

Here is a dummy version of my situation: Any combination of first and last names is valid. I want to build a form for assigning tasks (and setting one as default) for each combination. It should look roughly like this: I can't seem to get this to work. If I have a "nameQ" query that just...

Another question (sorry to stack them up, I'm just getting some good help here): The reason I have the little gap in the subform there is so that when the list gets big enough to require a scrollbar, it doesn't crowd out the subform controls. Is there a better solution to that problem? Ideally...

Incidental question: As these subprocedures start to stack up for a given form, should I be making named modules within the form to organize them? Or is that bad?

Getting there! I like the way it's shaping up. Thanks for your help. (The drop down at the top toggles the subform.) It's a good question. The original idea was that the user could edit them, but to commit the edits, they would have to click the "Save" button (so yes/no, in response to your...

Okay, I'm sorry: I'm having a hell of a time getting the "New Record" button to make the subform footer visible. I'm trying stuff like this: Me!subform!FormFooter.Visible = True Me!subform!FormFooter.Visible = True Me!subform.Form!FormFooter.Visible = True Me!subform.Section(acFooter).Visible =...

Okay interesting! Not exactly what I had in mind, but it would work for sure. I played around and it didn't seem like it would be possible to get the footer to look exactly like a new entry--it doesn't play nice with the scroll bar, banded rows, etc. Maybe there is a way to do it. But honestly...

Umm, sure the question was open ended, but it wasn't ambiguous. I'm looking for a good (if not the best) way to accomplish what I've laid out in my "detailed description". I've seen forms like the one in my screenshot enough that I would expect there to be a good chance that someone on an Access...

Another idea I had is to turn off "Allow Additions" on the subform, have the "New Record" button add a record to the Category table with a dummy code value, set the focus to the subform, navigate to the new record with that code value, and finally delete the dummy code value, leaving the user to...

I'm trying to build a form that looks like this: This mimics some forms that I've seen in commercial database software. It is a continuous form embedded in a single form, the latter of which has no data source. I want the buttons on the side to be the only way to add or delete records from...