hello,
I have D7-DOA 4.0.6-WXP-Ora8i the follwoing :
OracleSession1.Connected:=true; work ok at desgin time while it return error at runtime (TNS protocol adaptor error) why?

Rgrds

this is a pre-sale Q ,
can you help me pls.

This is an Oracle Net configuration issue. Do you have multiple Oracle Homes installed? Can you use SQL*Plus from all Oracle Homes to connect to this database?

Note that Direct Oracle Access will use the Primary Oracle Home by default. This is the Oracle Home that is listed first in the PATH environment variable. You can select a different Oracle Home by using the Oracle Home Selector (a standard Oracle utillity).

I have only one home ,i edit the the path Var. to point only to one home (I installed more than oracle ver. but now i have only one on my PC) ,but the runtime error still, at disgn time every thing is ok ?!

Rgds.
Rasheed

Does the executable have a working directory with parentheses in the path name? Oracle Net does not like this.

thanks for your help ,
no ,no parentheses in the path name ,
here are the details:
exe full name :
C:\Program Files\Borland\Delphi7\Projects\ODC\Project1.exe

here the sqlnet.txt :

***********************************************************************
Fatal NI connect error 12560, connecting to:
(DESCRIPTION=(ADDRESS=(PROTOCOL=BEQ)(PROGRAM=oracle)(ARGV0=oracleORCL)(ARGS='(DESCRIPTION=(LOCAL=YES)(ADDRESS=(PROTOCOL=beq)))'))(CONNECT_DATA=(SID=ORCL)(CID=(PROGRAM=C:\Program Files\Borland\Delphi7\Projects\ODC\Project1.exe)(HOST=RSHD)(USER=Rshd))))

VERSION INFORMATION:
TNS for 32-bit Windows: Version 8.1.7.0.0 - Production
Oracle Bequeath NT Protocol Adapter for 32-bit Windows: Version 8.1.7.0.0 - Production
Time: 06-OCT-2005 13:30:36
Tracing not turned on.
Tns error struct:
nr err code: 0
ns main err code: 12560
TNS-12560: TNS:protocol adapter error
ns secondary err code: 0
nt main err code: 530
TNS-00530: Protocol adapter error
nt secondary err code: 126
nt OS err code: 0

This is going to a local database on your PC. Is that correct? If not, perhaps you have enabled TOracleSession.DesignConnection? In that case the logon properties set at design-time (including LogonDatabase) will not be propagated to the runtime situation.

yes, you are true the problem was from TOracleSession.DesignConnection it was true ;
i set it to false ;
now evreything is ok
Many thanks