Subject RE: [firebird-support] C API - isc_attach
Author Dan Crea
Okay, I may have misunderstood your question. Are you saying in the
isc_attach_database method there is a failure which caused the process to
exit? That is, calling isc_attach_database never returns and thus the
status vector is never set?

Have you tried setting up a DPB and passing this during your call to
isc_attach_database instead of NULL?

Dan

-----Original Message-----
From: Roman Jokl [mailto:rjokl@...]
Sent: Friday, June 27, 2003 9:51 AM
To: firebird-support@yahoogroups.com
Subject: Re: [firebird-support] C API - isc_attach


Dan Crea wrote:

>Hello:
>
>>From you code example, it looks like you may need to specify a full path
to
>the database file. Not specifying a path will use the working directory.
>So running this binary elsewhere will not find the file. (I'm not 100%
sure
>on the working directory point...)
>
>Example:
>isc_attach_database(status, 0, "localhost/usr/local/firebird/kerio.fdb",
>&db, 0, 0);
>or
>isc_attach_database(status, 0, "/usr/local/firebird/kerio.fdb", &db, 0, 0);
>
>However, if the db file is not found you should get an error in the
>ISC_STATUS vector. You should copy this vector and pass the copy to
>isc_interprete(...) to see what the error is. Assuming (vector[0] == 1 &&
>vector[1] > 0) is true.
>
>Regards,
>Dan
>
>
>
>
no, this is not the problem, because:
1) i try full path
2) i run the binary in the directory which database is in
3) the attach function terminate execution, so i cann't test status vector

Jolly



Yahoo! Groups Sponsor

<http://rd.yahoo.com/M=251812.3170658.4537139.1261774/D=egroupweb/S=17051153
86:HM/A=1564415/R=0/SIG=11t6t7kdo/*http://www.netflix.com/Default?mqso=60164
784&partid=3170658>

<http://us.adserver.yahoo.com/l?M=251812.3170658.4537139.1261774/D=egroupmai
l/S=:HM/A=1564415/rand=766803331>

To unsubscribe from this group, send an email to:
firebird-support-unsubscribe@yahoogroups.com



Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service
<http://docs.yahoo.com/info/terms/> .




[Non-text portions of this message have been removed]