Following a comment by @sasakostadinovic9344, if you want to use this feature with linked ODBC tables, you need to tick the ODBC fields option in Access Options . . . Current Database . . . Filter Lookup Options. As the default is for this to be disabled, I suspect there may be a performance hit in doing so (untested hypothesis!)
Soooo simple! I can't believe I haven't thought about looking for a solution like this. I ended up with a bunch of unbound combos and a concatenation routine to set and clear the form filter 🙈 I bet you could even use an event handler function to keep the VBE cleaner.
Thanks for your feedback. The approach is indeed ridiculously simple but for various reasons, not widely known. Many developers go to all kinds of work-rounds to achieve this effect. You could indeed use class module events to remove duplicated code in the label headers or fields. That may be the subject of a future video
I've just finished updating the code to create a generic event handler for the header label events. (I've done 2 different methods). It was MUCH harder than I originally anticipated. The tricky part was transferring the code from the unassociated header labels to the field controls .I have uploaded the updated example app to a new web page:: www.isladogs.co.uk/multiselect-filter-continuous-form-2/index.html. At some point, I will also create a new video to accompany it.
I've just seen the edited reply read the article. Looks interesting. I'll be trying it out soon. Without knowing anything about the monitor position method, can you not simply convert using the ABS function?
@@nutsonbikes - No you can't use the Abs function as a work-around. However, the Access team have agreed to look into fixing this bug in the Accessibility function
Thanks. There will be more videos on continuous forms in the near future. In the meantime, I have an ever growing series of articles on extending the functionality of continuous forms. The latest article demonstrates how to freeze columns in a continuous form: www.isladogs.co.uk/freeze-columns-continuous-form-2/index.html.
@@IsladogsOnAccess i will Check that out. I have two problems i try to solve: first one is how to securely share my backend and how to do that, sharedfolder on lan or sharepoint etc second one is do you know a method to bind and track a specific feature such as entryID or GuID for particular email in outlook, so that when clicked it will pop up that email in outlook?
@@stanTrX You're digressing a long way from the subject of this video. For your first question, I suggest you start by reading my series of 3 articles on improving database security: www.isladogs.co.uk/improve-security/index.html. The 2nd article may be particularly relevant. As for the 2nd question, I suggest you ask in an Access forum. I use CDO for sending email from Access so Outlook is never used.
@11:15 That's weird, I've been using the Application.CommandBars method (thank you, BTW) in the column headers of a subform and I do not get this runtime error when I'm using the subform in its main form. I'm using Access 365 v2406, Build 16.0.17726.20078 64-bit
Hi. Just rechecked in v2407 (Beta Channel). although both methods work in a continuous form, I still get the error using Application.CommandBars.ExecuteMso ("FiltersMenu") in either the Label_Click or FieldName_DblClick event of a continuous subform As DoCmd.RunCommand acCmdFilterMenu ALWAYS works and is less to type(!), I now always use that method.
@IsladogsOnAccess don't quote me but I'm fairly sure I tried it before and got a error saying you cannot use continuous form as a subform. So I never tried again. Going back a bit now mind.
@@joerichardson5669 The example shown was an unbound form which acted as a container for a continuous subform. That arrangement works fine. Have a look at the example database on the web page for this video. It also works if you have a single form and a continuous form e.g. as a simulated split form or two continuous subforms side by side etc.... You are probably thinking of the misleading message that is shown when you try to add a subform to a continuous form. Access 'helpfully' changes the main form to single. In fact even that can be overcome to some extent e.g. by placing the subform in the footer
I've checked and can confirm your findings. Nor does it work with linked ODBC tables in datasheets. Its fine with both local and linked Access tables I've just asked the Access team whether there is a technical reason for this or if its a bug.
Following a comment by @sasakostadinovic9344, if you want to use this feature with linked ODBC tables, you need to tick the ODBC fields option in Access Options . . . Current Database . . . Filter Lookup Options. As the default is for this to be disabled, I suspect there may be a performance hit in doing so (untested hypothesis!)
Soooo simple! I can't believe I haven't thought about looking for a solution like this. I ended up with a bunch of unbound combos and a concatenation routine to set and clear the form filter 🙈
I bet you could even use an event handler function to keep the VBE cleaner.
Thanks for your feedback. The approach is indeed ridiculously simple but for various reasons, not widely known. Many developers go to all kinds of work-rounds to achieve this effect.
You could indeed use class module events to remove duplicated code in the label headers or fields. That may be the subject of a future video
I've just finished updating the code to create a generic event handler for the header label events. (I've done 2 different methods). It was MUCH harder than I originally anticipated. The tricky part was transferring the code from the unassociated header labels to the field controls .I have uploaded the updated example app to a new web page:: www.isladogs.co.uk/multiselect-filter-continuous-form-2/index.html. At some point, I will also create a new video to accompany it.
I've just seen the edited reply read the article. Looks interesting. I'll be trying it out soon. Without knowing anything about the monitor position method, can you not simply convert using the ABS function?
@@nutsonbikes - No you can't use the Abs function as a work-around. However, the Access team have agreed to look into fixing this bug in the Accessibility function
your creativity is on another level wanted to learn more can
Thanks. There will be more videos on continuous forms in the near future. In the meantime, I have an ever growing series of articles on extending the functionality of continuous forms. The latest article demonstrates how to freeze columns in a continuous form: www.isladogs.co.uk/freeze-columns-continuous-form-2/index.html.
@@IsladogsOnAccess sure watching this also subscribed your channel
That is exactly what I was looking for. Thaaaaaaank you so much !!!!!!!! 👍👍👍👍👍👍👍👍👍👍👍👍👍👍
You're welcome. Glad you like it. There are many more similar items available on my website. See www.isladogs.co.uk/add-features-forms
This is very cool
Glad you liked it
Thanks
You’re welcome. There will be a follow up with a generic solution for use in any form in just a few days
@@IsladogsOnAccess i will Check that out. I have two problems i try to solve: first one is how to securely share my backend and how to do that, sharedfolder on lan or sharepoint etc second one is do you know a method to bind and track a specific feature such as entryID or GuID for particular email in outlook, so that when clicked it will pop up that email in outlook?
@@stanTrX
You're digressing a long way from the subject of this video. For your first question, I suggest you start by reading my series of 3 articles on improving database security: www.isladogs.co.uk/improve-security/index.html. The 2nd article may be particularly relevant.
As for the 2nd question, I suggest you ask in an Access forum. I use CDO for sending email from Access so Outlook is never used.
@11:15 That's weird, I've been using the Application.CommandBars method (thank you, BTW) in the column headers of a subform and I do not get this runtime error when I'm using the subform in its main form.
I'm using Access 365 v2406, Build 16.0.17726.20078 64-bit
Hi. Just rechecked in v2407 (Beta Channel). although both methods work in a continuous form, I still get the error using Application.CommandBars.ExecuteMso ("FiltersMenu") in either the Label_Click or FieldName_DblClick event of a continuous subform
As DoCmd.RunCommand acCmdFilterMenu ALWAYS works and is less to type(!), I now always use that method.
@@IsladogsOnAccess That's right, if it's less to type and always works, that's the way to go.
A continuous sub form . ? That's new to me 😮
Really? I use them all the time
@IsladogsOnAccess don't quote me but I'm fairly sure I tried it before and got a error saying you cannot use continuous form as a subform. So I never tried again. Going back a bit now mind.
@@joerichardson5669
The example shown was an unbound form which acted as a container for a continuous subform. That arrangement works fine. Have a look at the example database on the web page for this video. It also works if you have a single form and a continuous form e.g. as a simulated split form or two continuous subforms side by side etc....
You are probably thinking of the misleading message that is shown when you try to add a subform to a continuous form. Access 'helpfully' changes the main form to single. In fact even that can be overcome to some extent e.g. by placing the subform in the footer
@IsladogsOnAccess ohhhh I see thank you for that. I will certainly be giving it ago
It looks like this method does not work on forms based on ODBC-linked tables.😒
Interesting. I'll investigate further
I've checked and can confirm your findings. Nor does it work with linked ODBC tables in datasheets.
Its fine with both local and linked Access tables
I've just asked the Access team whether there is a technical reason for this or if its a bug.
I've just written a separate reply explaining how to enable this feature for linked ODBC tables/fields