I have pin pointed the issue. After I sent out the e-mail, I dropped the
OPENING table in my test database, I then tweaked to the create script for
the OPENING Table by removing the following line:
ALTER TABLE OPENING ADD CONSTRAINT FK_OPENING FOREIGN KEY (PROJECT_ID)
REFERENCES PROJECT(PROJECT_ID
I've set one up by creating an empty database with two of the tables the
give me issues.
My feeling is that it has something to do with the Foreign Key that one
table has to the other.
The following assumes that DDEX has been configured and setup with Visual
Studio 2010:
Attached are 3 scripts:
Thank you for your quick answer,
Marc
-Message d'origine-
De : Jiri Cincura [mailto:disk...@cincura.net]
Envoyé : mardi 3 août 2010 13:55
À : For users and developers of the Firebird .NET providers
Objet : Re: [Firebird-net-provider] Transaction configuration with the
ADO.NET Data provid
On Tue, Aug 3, 2010 at 10:36, Marc Bettex wrote:
> new FbTransactionOptions()
> {
> TransactionBehavior = FbTransactionBehavior.Concurrency |
> FbTransactionBehavior.Wait | FbTransactionBehavior.LockWrite |
> FbTransactionBehavior.Protected
> };
You can't specify table for locking, it's no
On Mon, Aug 2, 2010 at 20:44, Luis Rizo wrote:
> Anyone have any input or feedback on this issue I'm having?
Do you have any reproducible testcase?
--
Jiri {x2} Cincura (x2develop.com founder)
http://blog.cincura.net/ | http://www.ID3renamer.com
Hi,
I'm currently using the ado.net firebird client 2.5 and I have some problems
with the configuration of the transactions. I only found some outdated
documentation from version 1.7 on the web, so I was hoping that someone
could point me toward some up to date documentation or tell me how to solv
