Hi,
I recently discovered that I have been making a design mistake when using SQL Server views. I previously would have a view and allow the user in an Access form to change data in the view.
However, I learned that this is not a good solution. A better solution is to have the user make their updates on a table.
My question is that I have a form in Access that is a "Continuous Form." The user enters the data into this form which is linked to the MS SQL Server table. However, they want to see the calculated values that result of changes made in the table.
Is the best way of doing this to have 2 subforms where one is linked to the SQL Server table and the other is linked to the SQL Server view and then they are synchronized and whenever a change is made to a record in the table, it updates the subform showing the view for that record? And then returns to the exact record where the change was made?
It isn't completely clear what the correct solution here is. Though, it is clear that linking directly to the view for edits and data entry can and does result in issues and confusion for SQL Server. Thanks!
Best Regards,
c
I recently discovered that I have been making a design mistake when using SQL Server views. I previously would have a view and allow the user in an Access form to change data in the view.
However, I learned that this is not a good solution. A better solution is to have the user make their updates on a table.
My question is that I have a form in Access that is a "Continuous Form." The user enters the data into this form which is linked to the MS SQL Server table. However, they want to see the calculated values that result of changes made in the table.
Is the best way of doing this to have 2 subforms where one is linked to the SQL Server table and the other is linked to the SQL Server view and then they are synchronized and whenever a change is made to a record in the table, it updates the subform showing the view for that record? And then returns to the exact record where the change was made?
It isn't completely clear what the correct solution here is. Though, it is clear that linking directly to the view for edits and data entry can and does result in issues and confusion for SQL Server. Thanks!
Best Regards,
c