Search results

I guess what I meant was that it shouldn't change how this code works. Sorry for the overly broad statement.

Reports are not editable. I think you are going to need to make a Word template, and use VBA code to instruct Access what to do with it. I have no experience with that, though others might.

Well to be clear, it's only possible with a "hack"...like the text box on top of a combo box trick. But the thing is a continuous form isn't really necessary for this design. He only needs to be working on one form at a time, so use a record list, then click one and have it pop up to work on it.

Try a full decompile and recompile: https://www.access-programmers.co.uk/forums/threads/how-to-tell-when-an-access-database-has-maxed-out-on-total-number-of-objects.310767/post-1684991 Access updates have no bearing on your VBA code except in circumstances of changing bit depth. Otherwise...

I can't vouch for it as I haven't used inventory, but there is a working example in the Northwind Traders database from Microsoft. Look in the templates, it may give you some ideas.

You cross-posted this here: https://www.access-programmers.co.uk/forums/threads/query-not-working-by-changing-field-type-from-number-to-text.311337/ And the answer several have given you is to link the Master and Child fields. Best practice is to link them with the Primary and Foreign keys...

I understand your goal and will say that there is a limitation within Access in doing this the way you describe. You can not "cascade" combo boxes in a datasheet or continuous form. That means you can't have a combo box filter a second combo box. The workaround would be to have all the combo...

Another option, unless you want more sophisticated graphics, is to use unicode characters. This would work in any version of Access.

I'm not sure a list box is the correct method. If using a subform, just choose datasheet or continuous forms, and use the link Master and Child fields in the subform's properties.

None of this would be necessary if using link Master and Child fields in the subform properties. Look on the Data tab. But...if you insist on using search for record (not necessary) The macro builder helps you by suggesting field names when you begin typing. I would just double click those...

That is handled by queries and reports. A query can be designed to gather the data you want, sort, group, sum, etc, and output to Excel, where it could then be formatted as desired. Crucial will be collecting and storing it in the right format, as described above. These queries will not work...

Use this expression as the source for txtTotalReceived: =IIf([PurchaseOrderID]>0,DSum("QuantityReceived","Purchase Order Details","[PurchaseOrderID]=" & [PurchaseOrderID]),"") (y)

I'm trying to write an expression in place of the existing calculated field. But, your PurchaseOrderID is displaying as Purchase Order ID in some places which is causing a lot of confusion when switching views and writing the expression... By the way, your Purchase Order Details has no primary...

I don't think the calculated field is the problem = I changed your code to refer to the subform field directly and it still didn't work.

If I change the > 0 to = 0, the button is disabled. This is evidence that the value isn't what we think it is.

My $0.02 is that this would be easier with two command buttons, but I understand wanting to consolidate them. Actually, it could probably still be done with just one command button. Worth a try...

Check it again. If you open an order that has all 1s, the caption is not displaying properly because it is based not on the total quantity, but on whether or not the button has been pressed. I'll keep thinking about this but for now my gut tells me there is other code conflicting with your...

I just stepped through the code and it appears you have an infinite loop here?

You could make it so that the caption of the toggle button is based on your subform footer count, but that doesn't appear how it is currently set up. It appears that the caption is based on whether or not the button is pressed (true or false). Here is the current code for the toggle button...

I just had a look at your database. First, this is a toggle button and not a command button, so that might change how people reading this understand the problem. Now, what I'm seeing is the button displaying "Set to Received in Full". Pressing it sets all items Quantity Received in the subform...