Closing two Recordset issue

No, because that record is added through the first query, there won't be a new record when the next query runs.
 
the Next Step is to identify and point out the changes

Okey the next step. showing the user what changes by color coding or some other way to make it clear to user which fields was changed.
From top of my mind the only thing that comes to mind is using vba to identify which value was changed. i dont know if there is easier way to do that without vba. Because now you will have to identify where the change occured and display it by color coding. with a recordset i can use select case and identify where the changes occured. I really want to avoid using recordset. The solution you gave me work great but now i need to identify the values that was changed. any ideas or suggestion to kick me in the right direction.
 
No, this would not identify which field(s) a change occurred in. I think that what I've suggested, might be a possible solution to the initial requirements, but does not address these new requirements.

Which means, the first step, and what you've now presented as the next step, probably won't work together.

This probably means that you'll probably need to go back to the drawing board again, and rethink the strategy. You would probably need to do different things when only one field is changed vs more than one, vs new record, which I don't think your initial code/requirements included either.
 
i think the solution that you gave me will be building blocks for the next step

I gonna use your code to get the records that has changed or new records into the table. From there i am going to use recordset to compare each line. it wont be alot of comparisong since i know which records has changed. From there i think i will be able to show where the changed with vb coding and recordset.

Thanks for all your help
 

Users who are viewing this thread

Back
Top Bottom