Issue when manipulating tables in Microsoft SQL 2005
We have a VB Invoice application where the detail lines are unlimited. Up to now the max of detail lines are a bit over 700 lines.
Users can create an invoice, save it and later on another user modifies it. One specific invoice can be worked by at least 4 user ate different stages. But no 2 users can work with the same invoice. However, at least 7 users have each an invoice working with it.
The problem we have is when user are saving the invoice.
We had issues of the process stops or takes too long, but most of the times, it just get uninterrupted and the user looses their entry that can be at least 20 to 50 lines.
So we are looking for EE insight on proper process of saving so the apps stops being interrupted or takes too long.
Microsoft SQL Server.NET ProgrammingVisual Basic.NETMicrosoft SQL Server 2005SQL
8/22/2022 - Mon
This is the best money I have ever spent. I cannot not tell you how many times these folks have saved my bacon. I learn so much from the contributors.