C#

blackjack2150 wrote:

A man's gotta' do what a man's gotta' do. Even if it's not recommendable.

string[] members = Enum.GetNames(typof(FancyAnimal));
System.Collections.Specialized.StringCollection memberscollection = new System.Collections.Specialized.StringCollection();
memberscollection.AddRange(members);

string act ="dog";
if(memberscollection.Contains(act))
{

Vikram A Punathambekar wrote:

Why do you not recommend it? Because of the exception it could throw, or because it's slow?

public enum FancyAnimal
{
	dog= 0,
	cat= 1,
	squirel= 2,
}

public enum FancyAnimal
{
	dog= 0,
	cat= 1,
	squirrel= 2,
}

Vikram A Punathambekar wrote:

I assume you're trying to highlight the misspelling of Squirrel?

Vikram A Punathambekar wrote:

If the apps are unrelated, it doesn't make sense to make them share the same DB table for storage.

Vikram A Punathambekar wrote:

Personally, I would go for a readable representation like Dog rather than 0 in the database.

public class Patient
{
    private string[] m_labValues;
 
    public Patient(int labValueCount) 
    {
        m_labValues = new string[labValueCount];
 
        for(int i = 0; i < m_labValues.Length; i++)
        {
            m_labValues[i] = string.Empty;
        }
    }
 
    public string this[int index]
    {
        get
        {
            return m_labValues[index];
        }    
        set 
        { 
            m_labValues[index] = value; 
        }
    }
}

private Patient patient = new Patient(6);
patient[0] = "B.P is 120,80";
patient[1] = "Blood Sugar is 160";

dnahelix wrote:

public string LabValues
{
get { return m_labValues; }
set { m_labValues = value; }
}

public string PrinterNameText
{
    get
    {
        if(axPageLayoutControl1!=null)
        {
            return axPageLayoutControl1.Text;
        }
        return string.Empty;
    }
}