Search results

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.

As Duane said, it is possible to have a "non-normalized" form for data entry and save the data into "normalized" table by use of VBA. But why? Are you certain that 10 items is the forever upper limit?

Filter on range of what? What field are you applying criteria to - DateOfReceiving? Your dates are formatted for non-U.S. structure. Review http://allenbrowne.com/ser-36.html Post your attempted query SQL statement.

Fairly common topic. Review https://www.access-programmers.co.uk/forums/threads/max-of-multiple-columns.184618/ https://www.access-programmers.co.uk/forums/threads/finding-the-lowest-value-in-multiple-fields-issue-with-null.235721/

MajP, when you say "get rid of all lookup tables" did you really mean "get rid of all lookup fields"? Because surely the tables should remain?

Did my explanation clarify that it is not "safer" option and not appropriate for the requirement?

Labels have Tag property but not Value. So far, don't see any regular Access controls without Tag. If control's property does not have "clear", code should work, unless form includes ActiveX controls. I have a form with two Web Browser controls, each with different properties - one has Tag and...

Did you try it? Aggregate ignores records with Null in specified field. If no records, function returns Null (except for Count which will return 0) so calc Nz(fieldname,0) accomplishes nothing because there are no records for Nz() to work on and Sum(Nz(fieldname,0)) still returns Null when no...

Now use Nz() function. =Nz(Sum(fieldname),0)

I edited my previous answer and no longer has that suggestion because it did not work in my test. I should have tested before posting.

There is no Null() function. There are Nz() and IsNull() and Is Null. Testing for Null in main form textbox won't work because there is no Null, there is an error and the error will just propagate and textbox shows #Size! error. I did a test and when there are no records in subform, main form...

Reported in other thread that changing to 1 fixed problem. I finally examined the db and can see the issue. And I was able to replicate in my db.

RunSQL will trigger warning popup. Avoid that by turning Warnings off then back on after. Or use CurrentDb.Execute instead of DoCmd.RunSQL.