not null validation

[kkukreja]

Hi All ,

I am connecting oracle 11G database with access and then trying to create a form.
In the form we have to validate that the text filed is not null.

I have tried using this simple code :

if isNull(text0.text) then


msgbox "null values not allowed"
end if


but then its not working.. I am using it in before_update section.

which code should be used to verify that and also where should i pasting the code.
I have been trying to fix this since the last 2 days... but its not helping...

please help me..

regrads
kkukreja

[RuralGuy]

To catch Zero Length Strings (ZLS) as well use:
If Len(Me.text0 & "") = 0 Then
...and you will notice I used the default .Value instead of the .Text property. The .Value property *is* valid in the BeforeUpdate event.

[kkukreja]

Thanks Sir..
i have 2 more questions :

1.How to display column names in the list box ?
2. Also in my SQL queries I have column aliases that i cannot give with access.. is there any way to use column aliases while using sql queries in access..

thanks and regards
kkukreja

[RuralGuy]

I believe you will find that Display Column Headings is a property of the ListBox Object.

[kkukreja]

Sir ,

You mean column heads right ? Thanks.. yeah i found that option..

and just please tell me about the column aliases... i have used NZ for NVL ( in SQL) but what should i use to display columns aliases everywhere..

thanks
kkukreja

[RuralGuy]

I didn't answer that question because I have no idea what you are talking about, sorry.

[kkukreja]

I didn't answer that question because I have no idea what you are talking about, sorry.

Sir ,

SORRY if i confused you..

what i mean is :

suppose i have this sql query :

select name 'USER NAME',address 'LOCATION' from table;


then the aliases that i am using (USER NAME, LOCATION) cant be used and it throws an error...

how do i used aliases(a different name for column for displaying purpose only) in SQL query that i am accessing from ACCESS..

thanks
kKukreja

[RuralGuy]

Enclosing things in [brackets] will generally keep Access from getting confused.