If you will be adding other options later you may be better with the lookup
table.
For now I would do:
No = -1
Not Applic = 0
Yes = 1
Although using 1, 2 & 3 presents no particular problem.
[quoted text, click to view] "Dinghy" <Solutions@nospam.NavigoDesign.com> wrote in message
news:bFpff.1124$pF.75@fed1read04...
> Hey All,
>
> I am very early in the development of the Database and the ASP page and
> looking for the opinions of the Gurus for an approach that will give me
> the best page performances.
>
> I am building a form which will have several "Yes/No/Not Applicable"
> questions. The page will send the data to an Access Database.
>
> I am setting up the DB fields where the values for Yes = 1, No = 2, Not
> Applicable = 3. The Default Value for each field is 3. In a seperate two
> field table, t_YN, I have the the options, Yes/No/Not Aplicable. I then
> setup a one-many relationship between the two tables.
>
> My questions are, is this the best way to go? Or should I forget about the
> t_YN table and setup an IF...Then... Else function in ASP?
>
> IF t_Bat.BTyp = 1 THEN
> str_BTyp = "Yes"
> ELSEIF t_Bat.BTyp = 2
> str_BTyp = "No"
> ELSE str_BTyp = "Not Applicable"
>
> Another option is to store the actual text Yes, No, or Not Applicable in
> the Database. But won't this make the database larger than using an
> integer?
>
> I also had thoughts of using a Select IIF query in the DB and
>
> IF t_Bat.BTyp = "" Then
> str_BTyp = "Not Applicable"
>
> Which will work best? Or is there another option that I am not seeing yet?
>
> Thanks so much to all.
>
> Jim
>
>
>