Button on Subforms - showing related records

[MatthewB]

If I create a continuous form and then put a button on the record row to open the related record in a form it works. When I try to do this with a continuous form as a subform it doesn't. Furthermore the button wizard does not open. Is there a common understood reason for this? Thanks

 

[theDBguy]

Hi. When you say it doesn't work, can you please describe exactly what is happening? Are you getting an error message? If so, what does it say?

 

[The_Doc_Man]

That type of control doesn't work in continuous forms, because a continuous form considers all rows in the form's Detail section to be the same row for control purposes. You cannot put a control on the record row because ALL rows are the record row. More specifically, every row of a continuous form is driven from the same definition - the continuous form's design-view detail section, which defines every row to have the same appearance. There IS such a thing as conditional formatting to, for example, alternate colors on rows or to highlight a field in some rows, but that has nothing to do with the "buttons in continuous rows" problem.

You could put buttons on the sub-form in a non-detail section, either a header or footer. Of course, that means when you click something, your cursor is not on a row to be identified. Here is a discussion and sample of some code that would highlight the selected record.

How to Highlight the Current Record in a Continuous Form

Step-by-step instructions for applying a custom highlight to the currently selected record in a continuous form in Microsoft Access.

nolongerset.com

You could have a click event on a particular field in the continuous form and have that event (which is the same for EVERY ROW) go in to determine which is the form's .CurrentRecord, and there are other ways to deal with that, like have a bound checkbox as a field called "SelectedMe" - and if you click that box, since it is bound, it only affects one record. So you could have it identify the record by the fact of being clicked and then reset the value once you know which row you are looking at. Many ways to skin this cat.

 

[CJ_London]

what code do you have behind your button?
and what is the sql to the recordsource to the form you are trying to open to display the related record?

I suspect one or the other or both are not taking into account the fact the button is on a subform

 

[JonXL]

That type of control doesn't work in continuous forms, because a continuous form considers all rows in the form's Detail section to be the same row for control purposes. You cannot put a control on the record row because ALL rows are the record row. More specifically, every row of a continuous form is driven from the same definition - the continuous form's design-view detail section, which defines every row to have the same appearance.

I've used buttons on continuous forms many times. For continuous forms, Me.{whatever}should refer to the record currently selected.

 

[The_Doc_Man]

I believe the problem relates to which kind of button the OP was discussing. For some actions, you are correct - Me.xxx should indeed refer to the current record. But if you did Me.control.BackColor=0 from a continuous form, it does not refer to the currently selected record. ALL of the .control back colors will fade to black at once. That is why conditional fomatting is needed on continuous forms.

 

[JonXL]

Yep. Can't do conditional formatting like that except to 'fake it' as you point out. I might have missed that on your first post.

I think the OP is running into an issue trying to reference the subform as a subform from the subform, which doesn't work. He'll need to do the reference with a simple Me.ID (for example).

 

[MatthewB]

It is not opening the related record.

 

[MatthewB]

Yep. Can't do conditional formatting like that except to 'fake it' as you point out. I might have missed that on your first post.

I think the OP is running into an issue trying to reference the subform as a subform from the subform, which doesn't work. He'll need to do the reference with a simple Me.ID (for example).

Hello JonXL
Sorry but I am painfully new to Access. Me.ID. How does that help?

 

[CJ_London]

@mathewB so far you have described your issue, not shown it. Makes it difficult for us to provide you specific advice, only point you in what we believe to be the right direction for you to sort out yourself. See this link for how to reference controls in a form from other places.

Forms: Refer to Form and Subform properties and controls

 

[MajP]

There is no reason this should not work. So that means your code is incorrect. But we cannot guess at what your code is. However it should be identical to the code in the main form.

 

[Auntiejack56]

The OP is quite right. He is talking about design view, the cue being his reference to the button wizard.

When you create a continuous form, and drop a button on it, the button wizard opens.
If you then add the continuous form to a main form as a subform, the behaviour is different. If you drop a button onto the subform in this configuration, the wizard doesn't open.
To answer the OP's question, I haven't a clue why this happens - I never use the button wizard!!

Jack

 

[JonXL]

Hello JonXL
Sorry but I am painfully new to Access. Me.ID. How does that help?

Where is your button and what action is it supposed to carry out?

 

[Pat Hartman]

I never noticed that behavior before. Is it new? I always turn off the wizard anyway since I don't want embedded macros under any condition.

Edit the subform by opening it directly instead of as a subform. That may be why I don't see any difference in behavior. I don't build subforms while the are embedded. I build them separately and embed them later. By that time all the objects are created so I rarely change anything except code or maybe move stuff around.

 

[MatthewB]

Here is a redacted DB. On the stratas list form hit the button you get the related record. On the Stratas Form Detail in the Contracts section - I cannot set up a button to take me to the related record. The data resource is the Contracts_T. Since this button is within the record I thought it would be 'self-referencing' like on the stratas list. Thoughts? Thanks

 

[Pat Hartman]

I told you EXACTLY how to solve the problem. Here's a picture. The wizard pops up when I add a new button to the subform PROVIDED I open the subform directly.

 

[MatthewB]

WHEN PEOPLE START USING UPPER CASE IT IS LIKE BEING SHOUTED AT. On the other hand, when people use sentence case you feel like you are in a conversation. The administrators should force all formatting into sentence case with underlining for emphasis.

 

[Pat Hartman]

Sometimes, when you answer a question and the poster doesn't hear you, you need a little emphasis. If you don't want my help, block me.

 

[MatthewB]

Pat Hartman. Is that what you do? Shout at people who don't hear you. I read the you are a staff member. You should temper your ego.

 

[CJ_London]

@MatthewB - we are now on post#19 for a question that should only have required a couple of responses. We are all volunteers here and your reluctance to provide any meaningful information is frustrating. Criticising those trying to help will not earn you any brownie points.

I've taken a look at your db - finally found what I believe to be the right form (stratas_F_C) and taken a look at the the button which has an embedded macro, not vba as we have been talking about. Adding a new button opens up the wizard. Wizards do not work on existing buttons.

I don't use macros as they are notoriously difficult to debug when things don't work as expected, but I do notice you are trying to open the other form using the strata name, not the ID.

What I don't see is where your problem is per post #1 'continuous form as a subform'