Search results

If several users rush to work on the same record and then work on it practically at the same time, then you should first check your work organization. If there is a pile of tasks, not every user has to reach for the same task, but as a first step the developer can ensure that the closest record...

The error is not in the suggestion, but in your implementation.

WHERE Grade = Forms.A.Combo1 OR Forms.A.Combo1 Is Null The records displayed are those where the filter criterion evaluates to True. I answer in SQL because a query is passed to the DB machine as SQL and executed there as such.

What would change in the view if you were dealing with 4 or 5 units instead of 2? One approach would be to differentiate the application into input, storage + processing and output. The preferred unit would then be derived from the predominant processing, so that few conversions are necessary...

No. A table must be declared (in the FROM part) before fields from it can be used in the query.

Do you know which database management system the tables with data are in, or are you already rowing in the fog?

Faith is rarely helpful in serious situations. If a query is used as a data source, it will be executed in addition to the new query, in the worst case multiple times instead of once due to the correlated subquery. This will increase or even duplicate the effort and runtime. Design problems...

What indexes are there in your table? 700k records are a challenge, especially since a correlated subquery is used here. Without usable indexes it will be a disaster. The connection between index and efficiency should be common knowledge.

Does it help if you check whether the record can be written without errors by locking it before the actual editing = start of the Recordset.Edit? Approximately ' focus on the desired record With Me.Recordset .Edit .Fields("xy") = .Fields("xy") .Update ' if no error .Edit '...

This becomes, when viewed daily: Dcount("*", "filtertable1", "unitprice <= " & filtertable1.unitprice & " AND orderid= " & filtertable1.orderid & " AND odate = " & Format(filtertable1.odate, "\#yyyy\-mm\-dd\#")) AS PriceRank The calculation of PriceRank via DCount has a systematic performance...

Doing it completely differently is of course also a way to avoid making certain errors. There are different ways to pass parameters to a query. https://www.access-programmers.co.uk/forums/threads/query-to-find-records-not-between-two-dates.328481/page-2#post-1886589 I am one of those who want...

Anyone who thinks they will only make one error is an optimist. The procedure only gets stuck at the first error. https://www.w3schools.com/sql/sql_update.asp - This is not an append query, but an update query. - The unfinished formatting of the expression for a date has already been pointed...

If you are talking about multiple databases, you probably already have tables. To provide information about your development status, you should show the database schemas. MS Access is a development environment. Whether you can find a solution for such simple things as mentioned depends...

Calculations ... is a broad word that can be filled with many different meanings. More specific descriptions would have to follow.

Number of joins in a query: 16 https://support.microsoft.com/en-gb/office/access-specifications-0cf3c66f-9cf2-4e32-9568-98c1025bb47c

Correct. It is important to explicitly point out that automated services running in parallel require resources of their own and take them away from the main application. Regarding the original question: There are several Find&Replace tools that cleanly perform renaming at any point in the...

Do we now have to discuss all conceivable variants? The variant in #5 works, even if it is complicated in several ways, as described. Because the data volumes are certainly very small, there will never be any performance problems thanks to the power of the processor, so you can calculate many...

First of all, you should always use correct and complete syntax. DoCmd.TransferText (TransferType, SpecificationName, TableName, FileName, HasFieldNames, HTMLTableName, CodePage)

All of these facts should be stored in tables and thus be able to be evaluated. So show the database schema (representation of the tables with their relationships). Knowing this is always the starting point of a query. You also have to take into account that SQL performs set operations =>...

Things like object name autocorrection and display of sub-data sheets are performance brakes and should be turned off during operation. In my case, they are already turned off in a new, empty database.