<div>
it does make sense for a single user.<br />
<br />
it does not if you expect multiple users to use the same process simultaneously.<br />
if each user needs to see all that is new regardless who inserted the rows, you can store an increment or date in your field and mark in a separate table that the user has reviewed rows up to some point.<br />
if each user needs to follow this same process for the rows he has been working on, you can store the name of the user that needs to do the review in your extra field and null otherwise.<br />
<br />
anything more complex will require an extra table.<br />
<br />
if you have an existing id which is likely, it might be more cost-effective in terms of used space to create a separate table to store the last reviewed row number rather than add a field to each rows in the table
</div>


<div>
Yes, Let your &quot;task relating to the new records&quot; perform an update of the field New.<br />
<br />
/gustav
</div>


<div>
Thanks for the input!<br />
<br />
In a multi user environment I could add two fields: NEW and USER. &nbsp;On INSERT, I can check YES for NEW and add the current user as well. &nbsp;That way I only update the items added for the specific user who has just added them. &nbsp;Adding the user is also a good way I keeping track on who actually added the record.
</div>


<div>
When doing batch processing, I use a BatchID. &nbsp;I have a table that tracks the batches so the first step is to insert a row into the batch table logging the batch. &nbsp;It includes whatever information might be useful later. &nbsp;At a minimum, it contains the create date. &nbsp;When the batch is an import, I also log the full file name that was imported. &nbsp; Then as each record is inserted, it gets tagged with the batchID. &nbsp;That way, you never have to update the record and you can actually look at old batches. &nbsp;The new/old flag doesn't do anything useful and won't work at all in a multi-user environment. &nbsp;Adding the user name is more helpful but it still has to be removed at the end. &nbsp;The batchID stays in the permanent record.
</div>


<div>
Hi Pat,<br />
<br />
Could you explain your method a bit more? &nbsp;In my example, I have a table called tblLabels. &nbsp;This table is used to record Item Barcode Lables being generated for asset tracking. &nbsp;A user can specify a customer name and quantity of labels to print. &nbsp;The action to INSERT them into the table runs and the user is asked if they want to print/view the new records. &nbsp;How would your method fit into this?<br />
<br />
Anthony
</div>


<div>
if you want each user to review his own lines, store the user's name in the extra field, and nullify the field once the rows have been reviewed.<br />
<br />
if you want something different, you need to be precise regarding your requirements : you may want each person using the app to see the record that were previously inserted in the same session for example and the system to forget what was done afterwards or if the user disconnects before reviewing, for example. in that case, you probably should just keep the list of ids in a variable and not bother touching the db at all.<br />
<br />
on the other hand, you may want some generic tracking in which case you'd need to store an incremental id or possibly a timestamp and the user's name with the row, and keep track in a separate table of the last id each user already reviewed.
</div>


<div>
<blockquote>
The other suggested methods including your own, give you one shot at printing the batch
</blockquote>
<br />
the yes/no field suggested by the author does not suffer such shortcomings : you don't update the field unless the user did review stuff. using a (possibly existing) autoincrement col and storing the point until which stuff have been reviewed in a separate table does not either. but anyway we don't know what is expected yet.
</div>


<div>
Is this for MS Access or MS SQL Server? &nbsp;You have included both so it is unclear what is your database.
</div>


<div>
The BE is SQL Sever and FE is MS Access
</div>


<div>
The backend does not really matter. You need to make clear your needs regarding older records. If you only need a one time proposal regarding the records added in the same session it is likely easier to keep track of the records in access but per session batch ids would work as well and help with tracking
</div>


<div>
Hi,<br />
<br />
Thanks for all the suggestions received. &nbsp;Just to clarify, when new records are added by a user into the table, the user is asked if they want to see the new items which have just been added and they have the ability to print details of the new records. &nbsp;That is why I need to track what has just been added to the table. &nbsp;There is no requirement to be able to 're-open' the batch at a later point of time. &nbsp;The user is given a simple YES or NO question. &nbsp;If they don't want to review what has just been added - that is it.<br />
<br />
Thanks
</div>


<div>
<blockquote>
There is no requirement to be able to 're-open' the batch at a later point of time. &nbsp;The user is given a simple YES or NO question. &nbsp;If they don't want to review what has just been added - that is it.
</blockquote>
<br />
then you should probably remember the added items in access. there is no point in modifying the db.<br />
<br />
but if you need to, generate or use a per session id, insert records with the id and all should work as expected. compared to your initial yes/no solution this is similar but will work if multiple users use the system at the same time.
</div>


<div>
<div class="content wysiwyg-content">
Hi,<br />
<br />
I have an INSERT SQL query which is contained within a LOOP action. &nbsp;When the LOOP is completed I need to ask the user if they want to run a task relating to the new records which were just inserted.<br />
<br />
My plan at the moment is to have a new field added to the table which the data is being inserted and name it NEW (yes/no). &nbsp;When new records are inserted, the insert query will assign them YES. &nbsp;At the end of the process when the user is asked if they want to see/print the newly inserted records I can then run a select query based on that table where the NEW field = true/1. &nbsp;Once this has run I will set all TRUE fields to FALSE.<br />
<br />
Does this method make sense? &nbsp;Am I going about this totally wrong? &nbsp;Is there a better and cleaner way of approaching this? &nbsp;Really happy to see suggestions of simpler coding.<br />
<br />
Thanks <br />
Anthony
</div>
</div>


Hi,

I have an INSERT SQL query which is contained within a LOOP action.  When the LOOP is completed I need to ask the user if they want to run a task relating to the new records which were just inserted.

My plan at the moment is to have a new field added to the table which the data is being inserted and name it NEW (yes/no).  When new records are inserted, the insert query will assign them YES.  At the end of the process when the user is asked if they want to see/print the newly inserted records I can then run a select query based on that table where the NEW field = true/1.  Once this has run I will set all TRUE fields to FALSE.

Does this method make sense?  Am I going about this totally wrong?  Is there a better and cleaner way of approaching this?  Really happy to see suggestions of simpler coding.

Thanks 
Anthony

Run an action on recently added records to a table

Microsoft Access is a rapid application development (RAD) relational database tool. Access can be used for both desktop and web-based applications, and uses VBA (Visual Basic for Applications) as its coding language.

Microsoft Access

Visual Basic for Applications (VBA) enables building user-defined functions (UDFs), automating processes and accessing Windows API and other low-level functionality through dynamic-link libraries (DLLs). VBA is closely related to Visual Basic and uses the Visual Basic Runtime Library, but it can normally only run code within a host application rather than as a standalone program. It can, however, be used to control one application from another via OLE Automation. VBA is built into most Microsoft Office applications.

Microsoft SQL Server is a suite of relational database management system (RDBMS) products providing multi-user database access functionality.SQL Server is available in multiple versions, typically identified by release year, and versions are subdivided into editions to distinguish between product functionality. Component services include integration (SSIS), reporting (SSRS), analysis (SSAS), data quality, master data, T-SQL and performance tuning.