Updating recordset

Posted by / 13-Feb-2018 01:37

Updating recordset

It means, that if your users are running an order explosion update or trying to schedule production order, the system will start iterating over all Invent Sum Log TTS records for all items, which somehow participate in the explosion.Since now we have several millions of transactions, it will take some time.ADO is the default object library for Access, but DAO is still available.If you use a DAO Recordset, you must explicitly reference it. Recordset Dim str SQL As String Dim lng Updated As Long rst. Hi guys, I'd love to see the existing 'filter By Formula' feature for ‘List records' to be implemented for (batch) deletion of a record set.This code was working correctly in 4.0.7 but when I upgraded to 4.1 beta2, the problem appeared. If you click them, you'll note that the "Double Param" button updates the value in the grid, but the "Single Param" does not.I'm guessing the store's datachanged event isn't firing...

When both libraries are referenced and both libraries support an object, VBA will assign the library with the highest priority. Explicitly referencing each object's library when you declare the object is better: Moving through the records in a Recordset is a common task, but doing so comes with a few hazards.

Since both installations use Weighted Average inventory model, routine inventory recalculation was causing some 2-3-5 millions of updates to Invent Trans table and, respectively, creation of the same number of records in invent Sum Log TTS table.

The worst part of it is that Invent Sum Log TTS table is locked in pessimistic mode.

In my previous post, I stated that Invent Sum Log TTS table is not updated after related inventory transaction was physically posted. In a while I had to make some performance tuning for a couple of installations, which suffered from bad inventory closing performance and overall conflicts between inventory closing and regular user work.

After looking closer onto the problem, in both cases, I found out that the main reason for performance issues is a large set of updates to invent Sum Log TTS table, coming from inventory closing/recalculation process.

updating recordset-34updating recordset-29updating recordset-85

Since all explosion update process is run as a one big fat transaction, all updated records in invent Sum Log TTS will remain locked till end of this transaction and all other users, trying to schedule another production order, which happens to share any of direct or indirect subcomponents with order being re-scheduled, will have to wait till the transaction ends.

One thought on “updating recordset”