Search results

There are specific rules defined in this forum that don't allow some types of content in posts from participants with less than 100 posts. I recall watching my post count grow to 100 so I had full rights.

Great to see you here Ken.

@Woodpecker has had less than 40 posts.

Place a text box in the subform header with these properties Name: txtAmtTotal Control Source: =Sum([UnitPrice]*[Quantity]-Nz([Discount],0)) Then change the text box on your main form to: Control Source: =[SaleDetails].[Form].[txtAmtTotal]

Can you take a screen shot of your error message or is that prohibited also? We can't see your screen.

I believe the number of posts required is/was 100.

I can’t help but question the hard-coding of values in expressions. I would think that the values might be unique values in a lookup table. Perhaps you want to include or exclude #7 and #9 in the future. If possible, I would add a field to a table that would group/categorize these values. Data...

You could also try: [NewLineDesc] Not In ("#1", "#2")

I didn't think it was too much older than 10 years so I googled it. There are a number of dates starting in 2011 but it suggests a public release in 2015

PBI is only 10 years old. To me, “500 forms” makes PBI even more attractive.

I would consider using PowerBI.

You could remove the qryOutstanding stuff and use a domain aggregate function like dLookup().

The OP stated “When I save the form filter” which isn’t the same as QBE.

I never use the table name in these situations. This also assumes you won’t have repeated field names from more than one table.

I don’t find it misleading. I don’t think it mentions “container” and it accurately describes “select all the controls”. I’m happy with the help text as you quoted it and have always expected the behavior.

Are you positive your fields are not zero-length-strings rather than Null? I have always used FieldName Is Not Null rather than Not FieldName Is Null

Any time I see a question asking about calculating across fields, I assume the table isn’t normalized. In this case, I would have created a payment table with fields: TransactionID, [ParentID], TransactionType, TransactionDate, and TransactionAmount. There would be three records rather than...

I have seen where separate columns are added for each range so in your case there would be three extra columns with either the appropriate value or 0. Then create a stacked bar chart and set the colors as you desire.

What do you mean by “that is by default sorted by the ID field”? Are you using an ORDER BY somewhere that sorts by ID? I would never assume records will display in any reliable order without some setting or SQL order.

I’ve created un-normalized input forms to match timesheets or other forms that make the most sense and provide ease of use for employees/users. The code to load for edit or save to a normalized table is trivial. I wouldn’t make my users change their sensible paper forms or data entry screens...