I'm trying to dissassemble the sqlite3.dll file because i want to know how the sqlite3_column_double procedure really works, as it doesn't behave as i thought. So i loaded the sqlite3.dll into OllyDBG and there i still am

How can i find out where the wanted procedure starts at?

I've downloaded the PE Explorer and there's a special export-viewer-dialog. But how is it possible to view the exports via OllyDBG?

IDA would be better, but it's commercial

kasake36, please check PM as soon as possible (links lost quickly)...
there is free demo version of excelent IDA
http://www.datarescue.com/idabase/idadown.htm

My way of debugging DLLs (when I don't have their source...)
Find entrypoint by another SW or handy by calculating from dll header or find some interesting part in DLL with disassembler.
Replace the first byte of the first instruction of this part with byte CC by hexa editor
Under debugger load exe which uses DLL
Debugger stops in breakpoint in DLL
Replace the breakpoint byte with the original byte.
Simple trace or step over...

Oh gosh! IDA is GREAT!!! I've never heard of this program before.

Feryno, thanks for all! The description of your way of debugging DLL's is very helpful!

here comes another link for IDA :
http://208.66.194.6/cracklab/_/ida_pro_4.9.0.863_advanced_full_wWw.CRACKLAB.rU.rar - 52Mb

I think warez is not allowed here.

Like Okasvi said, use private message instead of posting links in forum for hot software.
My opinion is that everybody must be good in disassembling/debugging, because it is great way to improve coding skills. Sometimes you have executable without source and you want to learn how it does something what you want to learn how to do it.
Now I have more time to explain my method of dll debugging:
The method of editing entry point byte to int 03 instruction is necessary only in case when dll is compressed/encrypted.
In case when dll isn't compressed/encrypted, you can load exe which uses dll, tell the debugger to show you address range where dll is loaded and you can simple place breakpoint where you want (using IDA before this is good choice how to find interesting position in code - instead of case when DLL is compressed/encrypted so IDA doesn't help you much)