Recent content by GustavBrock

That's the default behaviour seen for any control created. You should always rename a new control to something meaningful.

Try adding the Value property: Dim rs As DAO.Recordset Set rs = Me.RecordsetClone If rs.RecordCount > 0 Then rs.MoveFirst While Not rs.EOF CurrentName = rs!Name.Value CurrentAge = rs!Age.Value ......Do something etc. rs.MoveNext Wend End If rs.Close...

OK. So, before this thread goes completely crazy, perhaps we should look at your actual issue? What numbers do you have? What calculations should be performed? Examples that fail (cause the overflow)

With that many decimals, first cast to Decimal: Value = 1 / 1.95 ? Value 0.512820512820513 ? RoundMid(Value, 16) 0.512820512820513 Value = 1 / CDec(1.95) ? Value 0.5128205128205128205128205128 ? RoundMid(Value, 16) 0.5128205128205128 RoundMid which performs true 4/5 rounding is hosted...

This will do: SELECT Entry.Entry_N FROM Entry ORDER BY Val ([Entry_N]), Entry.[Entry_N]

Those are some valid points, Jason. Thank you. Major bump is that implementing these will break backward compatibility; a V2 may be needed.

Oh, that explains. No problem, thank you for the clarification.

There seems to be some misunderstanding here regarding my VBA.Cryptography First, Microsoft ActiveX Data Objects 6.1 Library is not referenced anywhere. The library uses native Windows API calls only. Although you can do many things in VBA, native calls will always be way faster. Next, the...

You'll need a small helper function for that: ' Format the count of days, hours, and minutes of Date1 as ' hours and minutes. ' By default, the local time separator is used. ' Optionally, specify a custom time separator. ' ' Example: ' Date1: #10:03# + #20:01# ' returns: 30:04 ' '...

You are making it too complicated. Just apply a date format to txtLocalSystemDate, and Access knows it will hold a date value: =DSUM("Covers", "tbl_Net_RestaurantBookings", "[CheckIn] = [Forms]![frmBackGround]![txtLocalSystemDate]")

Exactly. You will grasp the flow of this code in a split-second, while you will have to read the second example to get it. Not to mention the mess you will get should you need an else block.

You can let the form do the work, and it will update "automatically". Read about Priority Numbers in my article at Expert Exchange: Sequential Rows in Microsoft Access Full code at GitHub: VBA.RowNumbers: Links can be found in the attached file.

Oh, so why did you post the question?

Access SQL can't combine DISTINCT and aggregation. Try this: Public Function getBoxContent() oDB.Execute "DELETE * FROM counted", dbFailOnError sQry = "INSERT INTO counted ( Family, Infra, box, collection, Specimens ) " _ & " SELECT A.Family, A.infra, A.BoxNo, A.Collection...

It could have, but here we must realise that VBA is considered "frozen" by Microsoft; no new features can be expected to be added. BigInt and Datetime2 have only be added to partly maintain compatibility with SQL Server and Azure (Sharepoint, PowerApps, etc.). Above all, we would wish a new...