Using embedded FB v2.1.1.17910 as embedded, with .net client v2.1.0 on
WinXP.
After using the above client then closing the database connection, the
DB file is not actually closed until the app is closed - I can see the
file handle exist in process explorer.
Our app is actually two apps that both need access to the database.
Only one will attempt access at any one time, so there's no need for the
full DB server, but both need to be running at the same time (we also
have other reasons why we have to use the embedded engine, not the full
server, so the server is not an option). However, after closing and
disposing the database connection in one app, the other cannot be
started because the file handle is not closed.
Is there some caching option in the .net client that can be turned off
that I haven't seen? Or some similar option that can be turned off in
the embedded engine form the .net client?
I've also tried the latest versions of both the engine and the .net
client and this still happens.
Thanks in advance for any help you can give,
Jared
________________________________________________________________________
Fairbanks Environmental Limited is a company registered in England and
Wales with company number 03027771 (VAT number GB670659412).
Registered office:
The Technology Management Centre, Moss Lane View, Skelmersdale, WN8 9TN
Tel +44 (0)1695 51775 Fax +44 (0)870 242 9890
This e-mail has been scanned for viruses by Star, powered by MessageLabs
________________________________________________________________________
------------------------------------------------------------------------------
_______________________________________________
Firebird-net-provider mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/firebird-net-provider
