>>>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.

Something like:

DO CASE 
  CASE the issue is billing
 * Gather information about the issue such as billing amount, date of service, etc.
  oClass = CreateObject("BillingHandler")
  CASE the issue is something else
  * Store notes about the issue in RTF format
  oClass = CreateObject("NotesStorer")
  CASE etc
ENDCASE
oClass.ProcessIssue()

Of course you probably just want to create a single instance of each handler and store them in a collection or something. You could use a table with a list of valid issues together with the relevant class for the issue....