|
[x]
Posted via EE Mobile
|
|
| Search, ask, and monitor your questions on the go with EE Mobile. Visit Experts Exchange from your mobile device and never be out of touch again. |
|
|
|
|
|
[x]
The Solution Rating System
|
|
| With so many solutions, how can you tell which solutions are most likely to help you and which ones are not? To provide you with a tool to use, we rate our solutions based on various elements that most accurately determine if a solution is a quality solution. To explain what factors affect the solution rating, here are the elements we take into consideration when formulating our solution rating. - The Grade of the Solution
- The Zone Rank of the Expert Providing the Solution
- The Number of Author and Expert Comments
- The Number of Experts Contributing
- The Feedback of the Community
Your Input Matters
Because of the way the system is set up, the most important variable in this equation is you. As a member of Experts Exchange, you are able to cast your vote on the quality of the solutions in regard to how complete, accurate, helpful and easy to understand each solution is. When you provide your feedback, each rating is adjusted accordingly. So, if you see a solution that has a poor rating that you think is a good solution, let us know by rating it. As you do, the rating will be adjusted and will become more accurate for other members of our site. If you have any suggestions that you would like to make for our rating system, please ask a question in the Suggestions Zone of Community Support. Thank you! |
|
|
|
|
Asked by SueJStevens in Microsoft Access Database, MS SQL Server
I have an Access front end with a SQL Server backend. We are using linked tables in the Access front end. The tables are very small - (the largest being under 2000 records). I have added two new fields to caputre the data/time and user who last updates a record. I added on SQL Server a trigger which updates these two fields when any part of the record is changed. We now experience an error which we believe to be a latency issue which we want to resolve by changing the ODBC Refresh Interval from 1500 to 1. The error reads as follows: "The data has been changed." Another user edited this record and saved the changes before you attempted to save your changes. Re-edit the record."
When I change the ODBC Refresh interval from 1500 to 1, I can no longer recreate the error message. Can anyone provide me with a list of downsides to be aware of by changing the ODBC Refresh interval?
1:
2:
3:
4:
5:
6:
7:
|
CREATE TRIGGER [dbo].[trg_Table1_LastUpdated] ON dbo.Table1
FOR UPDATE
AS
UPDATE [dbo].[Table1]
SET RecModDtTm = getdate(),
RecModBy = suser_sname()
WHERE RID IN (Select RID From INSERTED)
|
20091111-EE-VQP-91 - Hierarchy / EE_QW_3_20080625
