Free Lessons
Courses
Seminars
TechHelp
Fast Tips
Templates
Topic Index
Forum
ABCD
 
Home   Courses   Index   Templates   Seminars   TechHelp   Forums   Help   Contact   Join   Order   Logon  
 
Home > TechHelp > Directory > Access > Track Changes < Form Backgrounds | Command Line >
Back to Track Changes    Comments List
Only Track Changes Upload Images   Link   Email  
Dan Jackson              
2 years ago
In this video, you show how to "copy" the information to the separate table prior to update. I've added an update vba as well to show what is was changed to. Great.

I'm planning on designing a simple continuous form to show these changes. My concern is, at the moment, data for ALL fields are collected at EVERY update.

To improve efficiency and reduce garbage data, how can we set it to only copy fields that have been changed
(For example, using
IIF [Table1]![Field1]=[LogTable]![Field1], "", <Field2>, <Field3> and so on

I hope my ragtag attempt at an IFF statement shows what i'm trying to do! Cheers
Richard Rost             
2 years ago
The EASIEST way to do it would just be to track the change in the AfterUpdate event for each field, and then save that data to a master log table:

Table, Field, From, To
CustomerT, FirstName, Richard, Rick


If you want that much insight into what specifically was changed. It's more work to set up, but will give you the results you want.
Dan Jackson              
2 years ago
Sounds perfect. I think the cost of more build work vs long term benefits is worthwhile. Not only will it make tracking the particular event in an "Incident" easier, it should also reduce the amount of date output too. Can we see an extended cut of this on the horizon at all? :)
Scott Axton            
2 years ago
Did you miss the one under the Members section above?

Or are you talking an extended - extended cut?   LOL
Dan Jackson              
2 years ago
That's the one! The SUPER Extended Cut!!!
Richard Rost             
2 years ago
It would work pretty much the same way. Just change the table structure and the SQL statement a little bit. No need for another super hyper massive extended cut.

This thread is now CLOSED. If you wish to comment, start a NEW discussion in Track Changes.
 

 
 
 

The following is a paid advertisement
Computer Learning Zone is not responsible for any content shown or offers made by these ads.
 

Learn
 
Access - index
Excel - index
Word - index
Windows - index
PowerPoint - index
Photoshop - index
Visual Basic - index
ASP - index
Seminars
More...
Customers
 
Login
My Account
My Courses
Lost Password
Memberships
Student Databases
Change Email
Info
 
Latest News
New Releases
User Forums
Topic Glossary
Tips & Tricks
Search The Site
Code Vault
Collapse Menus
Help
 
Customer Support
Web Site Tour
FAQs
TechHelp
Consulting Services
About
 
Background
Testimonials
Jobs
Affiliate Program
Richard Rost
Free Lessons
Mailing List
PCResale.NET
Order
 
Video Tutorials
Handbooks
Memberships
Learning Connection
Idiot's Guide to Excel
Volume Discounts
Payment Info
Shipping
Terms of Sale
Contact
 
Contact Info
Support Policy
Mailing Address
Phone Number
Fax Number
Course Survey
Email Richard
[email protected]
Blog RSS Feed    YouTube Channel

LinkedIn
Copyright 2024 by Computer Learning Zone, Amicron, and Richard Rost. All Rights Reserved. Current Time: 7/23/2024 2:07:14 AM. PLT: 1s