On 2/24/06, Adam <s3057043@...> wrote:

> > How do I check if there is something connected to the database
> which may be
> > gaining exclusive access? I know that I haven't initiated access to
> the DB
> > using any other applications.
>
> If you know that then this probably isn't your problem. But to test.
> When you 'know' that you have closed down all the programs that
> access the database, give it a few seconds then attempt to rename the
> file. The garbage collection may be running for a few seconds, but it
> normally finishes within seconds.
>
> >
> > How do I implement the TCP loopback connection for the database ?
>
> You use the connection string
>
> [hostname]:[path to database or alias]
>
> A local connection does not use the hostname.
>
> > Unfortunately, I am using the BDE components TQuery, TDatabase, etc.
> >
> > I believe it may be something internal to the opening of the
> database within
> > the code. I'll go and check that out now...
>
> Yuck. I think you may be in unchartered waters there. The BDE may
> well be opening it exclusively.
>
> Try and open two iSQL windows. It should let you without problems.
> Now with the iSQL windows open, try and open your application. If
> your application fails, then it must be attempting a local connection
> (I would not be surprised if BDE did that).
>
> It is a case of first in best dressed as far as connection modes go.
> If you are in with a TCP connection (which supports multiple
> connecting), then direct connections will fail. Conversely, if you
> are in with a local connection (which does not support multiple
> applications connecting), then you will not be able to connect with
> either local or TCP connections. I believe this is to avoid
> corruption.
>
> First though work out what it is that is locking out the second user.
> If it is not the BDE I would be surprised.
>
> Adam
>
>

At first I thought this was a problem on the Testing PC. But now I
can't even run the application at home, and it seems like other
untouched versions of the exe can't access the database giving the
same error.

At run time (after compiling) the linker gives the above errors.

The last change I was trying to implement ( were not fully tested and
implemented). Involved copying 'hdk3ctnt.dll' to System32 and trying
ti implement context sensitive help. But everything has suddenly
changed....where I could easily open an Isql window and test a
compiled application from BDS, or running a exe file, now I get
errors.

I tired what you said Adam, with two ISQL windows open, but even with
one open (or without) I get errors.

The Database path previously didn't used to work without the
'localhost:' reference before the C:\Path. This is true with the
compiled application (final exe file) and also at Design time by
setting Active to TRUE.

currently, I am able to connect to the database at design time as
previously done, so at least that hasn't changed..

so at this stage not even a single user can Open the DB using Delphi....

>
>
>
>
>
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
> Visit http://firebird.sourceforge.net and click the Resources item
> on the main (top) menu. Try Knowledgebase and FAQ links !
>
> Also search the knowledgebases at http://www.ibphoenix.com
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
> Yahoo! Groups Links
>
>
>
>
>
>
>
>

--



Analyst
B. Engineering, B. IT
A.N.U (2004)

M: +61 401 409 620
H: +61 3 9376 8580


"In life, always do right. This will gratify some people and astonish the rest."

— Mark Twain