>>>>I have a table called avIssues which contains patient issues. The issues stored in this table come in two basic types called IssueType and they are 'Billing' and basically everything else.
>>>>
>>>>There will be edit screens to allow the user to create and manage issue types. Right now there will be logic that says:
>>>>
>>>>

>>>>if the issue is billing
>>>>
>>>>  Gather information about the issue such as billing amount, date of service, etc.
>>>>
>>>>otherwise
>>>>
>>>>  Store notes about the issue in RTF format
>>>>

>>>>
>>>>The problem is that right now I need to determine if the item is a billing issue. I can see later on the client wanting code to take action based on different codes.
>>>>
>>>>The question is what's the best to set up the data so that I can code a CASE statement later? I could use a code in the table, but this doesn't seem like the best approach. Anyone have other ideas?
>>>
>>>Maybe design different classes to handle different issues. Instantiate/use the relevant class depending on the issue type.
>>>Regards,
>>>Viv++
>>
>>But the question still is how to make that determination without having some kind of code in table. I can't see any way around it.
>
>PMFJI,
>
>Just to elaborate a little on Viv's suggestion, you don't need any code in the table, just a class name and assembly name. The class could either implement an interface or inherit from a base class. There was a discussion about this in the Interfaces thread a couple of weeks ago.
>
>Bruce

This is all going to be on one screen. There will be a header section which has some info about the person calling in, and a dropdown to select the type.

If the user selects 'Billing Issue', then a pageframe on the form will display page 1, which will contain fields to gather info. If they select 'General Issue', then page 2 of the pageframe will be activated which will contain an RTF field where the enter general notes.

The problem is that I can see this ballooning into more than just these 2 pages. But the question is how to know reliably what page to activate based off the Billing Type selection. I would like to be able to create and display a page on the pageframe on demand. I guess I don't have much choice but to store a code in the Billing Types table.