Search results

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.

Proper syntax is: UPDATE tablename SET fieldname = form control name WHERE somecriteria Need criteria or EVERY record in table will get same data. Where is the VBA located? In what form and what event? Why do you need UPDATE action to save data? Is form and its controls BOUND? If you really...

Exactly what do you not understand about concatenation? Doesn't matter how many fields are involved, it's still concatenation. ="Z:\FSE\8. FSE - Storage\" & [UNIT] & "\" & [Howden Project No] & ".jpg"

Here's another curve. Round works when field is Float type. Be aware Round in Access uses even/odd (banker's rounding) rule.

Don't see what those queries have to do with functions and the issue I identified. Do you understand what I described? What change did you make in code? Did you add criteria for date range?

Record 347 with 348/349 should not be red because there is ANOTHER 347 record (subnumber 4) between 348 and 349 by date? Your code logic does not test for that date criteria. You have a test for: DocNumber > " & lowerDoc & " AND DocNumber < " & upperDoc This criteria has nothing to do with...

Why do you have IsTransferValid function in two places? One is behind form and one is in general module. The module procedure does not get used. Still not clear why 347 with 348/349 should not be highlighted. As is, it meets the criteria for Conditional Formatting.