Subject | Re: [ib-support] Problems in a multiuser environment |
---|---|
Author | Helen Borrie |
Post date | 2001-04-21T23:24:50Z |
At 05:02 PM 21-04-01 +0000, Dale F. wrote:
[snip]
The API Guide's "Working with Transactions" section also contains so valuable info about transaction parameters that is missing from the chapter in the ESG.
The Ops Guide's "Network Configuration" chapter will help you to get the connection string right.
Once you get your head around the basics, you will need to abandon TIBTable. In client/server, it is of no use to you except perhaps to hold a small lookup table in memory.
Your problem (all descriptions so far given) point to the following:
1. Your app is connecting locally to the database, not through TCP/IP.
2. Your app is not committing your transactions.
3. You are using an old, buggy version of IBX.
4. Possibly you even have the BDE hanging about your app somewhere e.g. a TTable that is making its own connection/transaction conversation with the database.
5. Possibly your app is connecting to a mapped drive (doesn't work in a multi-user situation, as explained in earlier post.
Overall, if you don't want to supply details of your connection string and your components, there isn't much anyone can offer to help you solve your problems.
Helen
All for Open and Open for All
InterBase Developer Initiative ยท http://www.interbase2000.org
_______________________________________________________
[snip]
>What would it take to make this simple application work in a multi-A knowledge of how transactions work would be a good start.
>application environment?
>Also, can you recommend documentation thatAs you correctly pointed out, the chapter "Working with Transactions" is missing from the Developer's Guide. On investigation, I found it in the Embedded SQL Guide (along with a bunch of other stuff you'll need to know!). If you are writing a Delphi app, you are not doing Embedded SQL - but there is very little in there that is specific to Embedded SQL. It's where you will find the "meat" about how things work.
>would help me?
The API Guide's "Working with Transactions" section also contains so valuable info about transaction parameters that is missing from the chapter in the ESG.
The Ops Guide's "Network Configuration" chapter will help you to get the connection string right.
Once you get your head around the basics, you will need to abandon TIBTable. In client/server, it is of no use to you except perhaps to hold a small lookup table in memory.
Your problem (all descriptions so far given) point to the following:
1. Your app is connecting locally to the database, not through TCP/IP.
2. Your app is not committing your transactions.
3. You are using an old, buggy version of IBX.
4. Possibly you even have the BDE hanging about your app somewhere e.g. a TTable that is making its own connection/transaction conversation with the database.
5. Possibly your app is connecting to a mapped drive (doesn't work in a multi-user situation, as explained in earlier post.
Overall, if you don't want to supply details of your connection string and your components, there isn't much anyone can offer to help you solve your problems.
Helen
All for Open and Open for All
InterBase Developer Initiative ยท http://www.interbase2000.org
_______________________________________________________