After looking at how a few change logs have been made. I'm thinking of a different way to do it. Effectiveness aside, I can test it to see how it runs. My current idea is to have all the tables on my backend "worth checking" to have a user and date/time field added. Then run a query to find the "X number" of most recent changes. The x number could be a number or everything in past week ect. Where I'm stuck is making that query populate a table on the backend to store the data say once every 10 minutes.
My setup I have a server which i work from the has the backend for everyone and my front end which is massive. I have no performance issues, hell i run my cad program, test other front end programs, browse the web for information, while running my large front end program that shows me up to the minute information. The other 10 users have desktop pc's that i need to improve hardware on but they cost $50 each so cant complain, and they work.
Only 3 users in total need to see this change log so the info being sorted by my server and stored / removed from backend would help data flow over the network.
My assumption right now is to create a new front end to run a simple main page with an on timer event that will read said change log query and post it to table while removing old information from table to limit bloating of data.
I don't bother posting unless I believe I cant find what i need and think someone else may have a use for what I'm doing as well.
My setup I have a server which i work from the has the backend for everyone and my front end which is massive. I have no performance issues, hell i run my cad program, test other front end programs, browse the web for information, while running my large front end program that shows me up to the minute information. The other 10 users have desktop pc's that i need to improve hardware on but they cost $50 each so cant complain, and they work.
Only 3 users in total need to see this change log so the info being sorted by my server and stored / removed from backend would help data flow over the network.
My assumption right now is to create a new front end to run a simple main page with an on timer event that will read said change log query and post it to table while removing old information from table to limit bloating of data.
I don't bother posting unless I believe I cant find what i need and think someone else may have a use for what I'm doing as well.