Ok, here's the scenario...
We have C# GUI app on w28 R2 RDS server. Multiple users log on to this server to use the application. I've not noticed any issues with that part so far. When UserA logs in and then runs through one complete cycle of the application (sequence of steps to complete their job function), they leave the app running (Instance1) and in some cases will minimze the app and come back later and accidentally start a new instance (Instance2) of the app and run through another full cycle of the app.
The problem...
When Instance1 stays running, there are some values stored in textboxes that are not cleared out until they begin to cycle through the next record. When the UserA goes to process a new record in Instance2 app, the result is the previous record overwriting
the current result because of the values in the textboxes on Instance1. Now I could clear the values of these text boxes (that would be too easy), but I suspect the issue here is that the 2 instances of the app are sharing the same texbox names and string
values in memory resulting in the first instance holding the values. So if I clear the texbox values, that would blank them out and in theory would effectively cause Instance2 to show blank values inserted into the database record.
So...I've been considering multiple solutions for this, but I want to choose the easiest simplest route since the app is due for a major rewrite in the next 6 months. For now I just want to fix this bug and move on. I've considered threading each instance of the app, but not sure if that will correct the memory space issue.
Anyone have any suggestions for this problem? The app properties are currently set up to run under "user" scope. Thanks.