Subject | Re: Multi-Station Interbase |
---|---|
Author | ded_spb@yahoo.com |
Post date | 2001-04-20T20:42:18Z |
--- In ib-support@y..., mss@s... wrote:
database as remote accordingly your network protocol, even on the same
computer where IB server works. If even one connection of 2 try to
work being connected locally, you will corrupt your database.
mode, I swear. I already recommended you all what I can and nobody
can do more until you don't become acquainted with transactions.
Best regards.
> Hello community,Dale, *.gbd file can't be shared. Make shure you connect to
>
> I am having a problem using an Interbase/Delphi application on
> multiple work stations at the same time. Here is what happens:
>
> I go into the application on one work station. No problem. Then I
> attempt to go into the application on a second work station that is
> sharing Interbase data.
database as remote accordingly your network protocol, even on the same
computer where IB server works. If even one connection of 2 try to
work being connected locally, you will corrupt your database.
> When the application reaches a Delphi "Post"the
> method, it simply "hangs" and goes no further. The moment I exit
> application at the first work station, the application continues todoesn't
> execute at the second.
>
> Here is an example of the line of code that causes this "hang up":
>
> IBTable1.Post;
>
> The application uses Delphi IBX components and specifically the
> TIBTable component in this instance. It feels like the first
> application somehow has exclusive "control" of the table and
> release this control until I exit. This seems rather rude andThis exclusive control's name is transaction in concurrency wait
> unfriendly (IMHO).
>
mode, I swear. I already recommended you all what I can and nobody
can do more until you don't become acquainted with transactions.
Best regards.