Dear Andrew

You are right ! That's it !
When running 2-tier (client + server app together in same computer)
concurrent
raise exactly "Lock conflict..."
When running 3-tier (2 clients in two different computers + server app in a
third computer + IB in another different, total = 4 computers ) concurrent,
in this condition app server freeze and clients too !
But IB no freeze ! Really ! It's a warrior !

Well ! I have to put BDE in a beatiful box and send it to the moon ! Or then
as longer as possible !

Please give me your opinion: For a kind of input using DBgrid(many records),
I need to execute many consistencies with Select in several tables ! If ok I
need to execute one Insert in other table and some updates in another
tables !
Is it correct first to execute a pessimistic lock in all that records and
then execute that sequence of business role ?

Thanks in advance

Best Regards

Jed

""csswa"" <csswa@...> escreveu na mensagem
news:ainee5+2q7p@......

> --- In ib-support@y..., "Jed Nicolau Filho" <jed@p...> wrote:
>
> > I have a 3-tier application using BDE ! (Maybe the Problem !)
>
> Exactly. Just do a search for BDE in this forum to understand the
> Pandora's Box of problems you are likely to encounter. BDE is not
> robust enough for large-scale C/S. Crickey, even Borland know this
> because they're phasing it out. Standard procedure is to recommend
> conversion to IBObjects. If I had a dollar for every time somebody
> converted their C/S app to IBO and said their problems miraculously
> disappeared... yeah, well, I'd only have about six dollars... but if
> I had a dollar for every time I exaggerated...!
>
> From the symptoms it sounds like it's your app server freezing, not
> the IBserver. How is the middle tier handling transactions and
> conflicts?
>
> > Using client and server app in the same computer, that issue raise
> > "Lock conflict on no wait transacation ..."
>
> Okay, so correct me if I am wrong here. When you run two instances of
> your app (client + middleware + IBserver) on the same computer, and
> attempt to update the same record in both instances, you get the
> standard IB lock conflict message and everything is fine: the first
> committed transaction goes ahead and the second fails (it does not
> wait, 'no wait transaction'). Or are you doing your test *without*
> the middleware?? More info!!
>
> Regards,
> Andrew Ferguson
> -- Must...drop...pantaloons!
>
>
>
>
> To unsubscribe from this group, send an email to:
> ib-support-unsubscribe@egroups.com
>
>
>
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
>
>
>