Search results

Appear to have fixed this issue in my db. TreeView ImageList property was not set to the ImageList1 control. Even though I set this property and build image list in VBA, seems to need this property set in design. Don't know if this was ever set because I remember this control worked fine when...

I get same error with your v18 file as well: "The expression MouseDown you entered as the event property setting produced the following error: There was an error loading an ActiveX control on one of your forms or reports." I OK past that then click on the TreeView +AppRIbbon item and get error...

My exercise did not involve custom class module. I built forms and controls from scratch. All code behind forms. Just downloaded MajP demo. Right off I get same error as in my db when opening form. Library reference is okay so that is not cause. I OK through error and form sorta works but error...

Would be nice to provide link to MajP's sample. Here is one thread with an attached file https://www.access-programmers.co.uk/forums/threads/majp-treeview.319019/ TreeView and ListVIew are ActiveX controls and come with their own set of issues and learning curve. Quite a bit of code...

As already mentioned by plog, probably don't need a table for Seasons. Season would just be a number field in Episodes table. Initial year of airing would be attribute of Series table. Except now I see the site offers data like Season Artwork and Season Trailers. If OP wants those details, a...

Where is SeriesID in that RowSource? How would that RowSource show all seasons for a specific show as shown in OPs image? Master/Child Links have nothing to do with listbox (or combobox) data.

I should have said earlier "couldn't be done and allow form data to be editable". If data editing is not important, a report can sit on a form, however, mouse scroll wheel won't work - have to drag scroll bar. Cheeky, I don't see how one listbox could show all seasons and appear as shown in OP...

Now I did a test that saved report/form with expression referencing field not bound to textbox. Still works for both in Access 2010 and 2021. I do remember this being an issue with Access 2003 and maybe also 2007 for reports but it changed, possibly with 2010. So if it's back, it's after...

How many listboxes would that be?

Pat, calc I suggested doing in query is ResultPromote value, not calcs using ResultPromote. In my test with Access 2010, ResultPromote did not have to be in textbox on report.

No. Including [] never hurts but not including can. As I said, Access will often add them in anyway (in queries and textboxes, not VBA).

Won't work because ResultPromote is not a field in report RecordSource (I tried it). Do ResultPromote calc in query and use query as RecordSource. Then reference field in Sum expression. This works. Quite possibly cannot do this calc in CROSSTAB query and will have to build another query that...

Did you mean "group by season"? Can sort by season but a form would not allow for a season header, at least not easily if at all. That would be feature of a report. I wonder what was used to code that GUI. I downloaded and ran it. Maybe part that broke is data download or requires establishing...

prabha, did you put "not" in the wrong position in that statement?

I've never worked with Runtime but from what I understand, that posted code should still work. Code that creates/modifies objects might not work. Don't need Call preceding DoCmd commands. Remove the parentheses. MkDir also does not need parentheses.

LarryE, The function is IIf, not Iff. I doubt that expression will resolve the #Error. Now I understand the DSum(). Arnelgp's suggestion should work.

Does the DSum() expression reference controls on subform? Why use DSum()? Do Sum() in subform footer textbox then textbox on main form references subform textbox. Regardless, subform must display at least New Record row. Why does subform not show New Record row?

Did you try suggestions in post 2?

Nope. Try ctrl + left click or "left click sweep select" method. Want to provide your db for analysis?

Even if data is not normalized, form design could still be BOUND for data entry and not need VBA running SQL. If you want to avoid popup warnings triggered by RunSQL, need to turn off/on with SetWarnings or use CurrentDb.Execute instead.