Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Capture event when form re-activated
Message
De
15/12/2008 08:57:10
Timothy Bryan
Sharpline Consultants
Conroe, Texas, États-Unis
 
Information générale
Forum:
ASP.NET
Catégorie:
The Mere Mortals .NET Framework
Versions des environnements
Environment:
C# 2.0
OS:
Windows Server 2003
Network:
Windows 2003 Server
Database:
MS SQL Server
Application:
Desktop
Divers
Thread ID:
01366727
Message ID:
01367399
Vues:
7
>>Hi Linda,
>>
>>>I have a form, which contains a tab page, from which a user can select a patient record and then open one or more data maintenance forms related to the selected patient. They are allowed to have multiple forms open but I don't want them to have one form open for one patient and another form open for a different patient. If the user comes back to the patient selection form while one of the maintenance forms is still open, I want to disable the patient selection grid. I have tried FormName.Activated(), FormName.Enter() and TabPageName.Enter() but none of them fires when I reactivate the form. I have managed to handle this another way but I'm sure I will need this behavior for something else one of these days. Where do I capture the reactivation of an open form? Thanks.
>>
>>Is this like a business rule they can only operate on one patient at a time (sorry for the pun) or is it a challenge of having multiple forms open that relate to a patient? I have an application that I participate in the maintenance that is similar in that we only want a single customer selected at a time. We have a form off to the side that is the customer selecter and they can only change customers by changing the selector which will relate any of the other forms. It is a bit of an odd way to do things in todays world, but sometimes you just got to do what they ask for.
>>
>>Anyway I didn't really have an answer to your question but was curious about the restriction on multiple patients.
>>Tim
>
>Tim,
>The issue is that, in a fast-paced, high-pressure environment, if they have a patient demographics form open for one patient and a case history form open for a different patient, it would be WAY too easy to put the information for one patient in another patient's data. I have the patient name everywhere but when people get in a hurry, they don't see that. Their current system is in access and basically has everything in 3 tables and data entry is a giant grid. They're not used to the multiple windows, so we don't want to tempt fate. Multiple windows for one patient is reasonably safe but for multiple patients it would be very confusing. I didn't want to have the selector change the data on the other open forms because I want to make sure they finish their edit sessions before moving on to another patient.
>Linda

Make sense to me.
Tim
Timothy Bryan
Précédent
Répondre
Fil
Voir

Click here to load this message in the networking platform