Recent content by MajP

What is your point? Great, you have code that sometimes works. What you going to do with that? That is the worst kind of bug, one that fails sometimes. Really hard to debug those types of errors. Read post 50 under specific conditions where it could work. But as everyone pointed out this is...

In the DSUMS you can do this in one recordset for the majority. ' Company.Add "taxblAmtA", Nz(Round(DSum("TaxableValue", "QryJson", "[InvoiceID] =" & Me.txtJsonReceived & "And [TaxClassA] = 'A'"), 4), 0) ' Company.Add "taxblAmtB", Nz(Round(DSum("TaxableValue", "QryJson"...

@June7 Sorry was doing this on my phone and could not see. You can still get it down to a 2 or 3 recordsets. For the dlookup, it should be simple to do one. Dim strSql As String Dim rs As DAO.Database 'Define variables Dim ItemCD As Long...

That opens only 2 recordsets. You are opening a recordset with each domain.

Make a new aggregate query that sums all of those values. Open it and assign a bunch of variables to those values that currently use drum. Open qyjson as recordet with your where condition. Save all those dlookups as variables. Use your variables.

I would be interested in you or someone else citing an example, because that is untrue as far as the application. There may be "confusion" but Access is not "ambiguous" . Any issue would be purely a user issue and have nothing to do with Access. The user might be confused what they are doing...

Actually that keyed me to the reason. The reason you still see it is because at one time it was the only method. Prior to AC 2000 there was only a recordsetclone and no recordset property. It was synched via the forms bookmark. So that was the required way to do it and has become habit.

Are you saying there are cases where even using bang notation will fail without a control on the form? I understand there are cases where compile time Dot notation will not work without a control on a form, but the run time bang always seems to works without a control far as I know. If so can...

I do not get the example either. It sounds as @Cotswold discovered something that is not an issue. I guess the bigger question is why did you believe you had to add the controls in the first place I do not get it because I see people do this all the time with people adding tons of hidden...

Unfortunately the data does not come to the OP in that format. The OP only gets the totals.

There is no need to. Main table has Region Total Sales Child table has Region PostCode You can link Main Table to child table using Region. Make Region the PK in the Main table and the foreign key in the child table.

So I asked Chat to do this. Public Sub PopulatePostCodes()Dim db As DAO.Database Dim rsSource As DAO.Recordset Dim rsTarget As DAO.Recordset Dim vCodes As Variant Dim i As Long Dim strCode As String Set db=CurrentDb Set...

Good question. Is that just a text field with commas or is it a MVF? I assume it is not an MVF because you would be able to query it just like any other query. If it is a simple text field you could easily write code (or simply have Chat do it) that would normalize your data by creating a...

My understanding is that it may work but it is not guaranteed. I have no idea why, so I asked Chat. Now I am not sure how much of this is truly accurate but here is the answer so take it for what it is worth. Short answer: it can work, but it’s not inherently “safe” unless you handle a few...

I see people use that a lot. Since that seems more complicated and since you posted it I assume there is some kind of advantage. I have no idea what that is. What is the advantage of that over this? Private Sub Form_AfterUpdate() Dim lngID As Long lngID = Me.TransactionID...