| Subject | IBObjects, Win2000 and XPpro |
|---|---|
| Author | Ross Garbig |
| Post date | 2004-04-27T01:59:03Z |
IBO4.3.A , IB 6.0.2.0 and Delphi 5,
I am testing a converted Delphi 5 Paradox app (currently using the TIBOxxx components) and getting some strange behaviour which I am having trouble tracking down. The app is an Interactive Voice Response system which manages up to 8 telephone lines to make reservations at sports facilities. I am using Dialogic D4PCI telephone interface cards and third party software which is the API interface to the Dialogic drivers. This 3rd party software is multi-thread. My application is not multi thread but is re-entrant with all database access forced to be single thread via a mutex. Not elegant, but it worked fine with the Paradox files on a file server. The converted app using TIBOxxx also forces access to the app gdb to be single thread also, with all queries having a short life span: open, do your thing and close within the confines of the mutex.
In the Paradox version I used a separate TSession for the Pardox database and tables. In the IB version I have employed a TIBOSession component and set the session property of the TIBODatabase and all table and query components to it. I assume this will isolate the database access from any VCL processing. The app dynamically creates 'n' MDI child windows in an MDI parent form. Each child just contains a memo component which is used to display call progress information for each call. With the same app in different environments I get different results such as:
XPPro(Pentium 4 class) , my app, Paradox files - works fine
XPPro(Pentium 4), my app, IB and IBO - call progress display disappears and some tel lines freeze forcing a task manager intervention to shut down
WIn2000, my app, IB and IBO - the same as XPPro
NT4/SP6, my app, Paradox files - works fine
NT4/SP6, my app, IB and IBO - seems to work OK .(still doing some stress tests but way better than XPPro or WIn2000)
I have gone through so many installs and uninstalls of software on different machines and still can't figure out where the problem might be. I am guessing that this is a session problem??. ANY guidance or tips would be hugely appreciated.
[Non-text portions of this message have been removed]
I am testing a converted Delphi 5 Paradox app (currently using the TIBOxxx components) and getting some strange behaviour which I am having trouble tracking down. The app is an Interactive Voice Response system which manages up to 8 telephone lines to make reservations at sports facilities. I am using Dialogic D4PCI telephone interface cards and third party software which is the API interface to the Dialogic drivers. This 3rd party software is multi-thread. My application is not multi thread but is re-entrant with all database access forced to be single thread via a mutex. Not elegant, but it worked fine with the Paradox files on a file server. The converted app using TIBOxxx also forces access to the app gdb to be single thread also, with all queries having a short life span: open, do your thing and close within the confines of the mutex.
In the Paradox version I used a separate TSession for the Pardox database and tables. In the IB version I have employed a TIBOSession component and set the session property of the TIBODatabase and all table and query components to it. I assume this will isolate the database access from any VCL processing. The app dynamically creates 'n' MDI child windows in an MDI parent form. Each child just contains a memo component which is used to display call progress information for each call. With the same app in different environments I get different results such as:
XPPro(Pentium 4 class) , my app, Paradox files - works fine
XPPro(Pentium 4), my app, IB and IBO - call progress display disappears and some tel lines freeze forcing a task manager intervention to shut down
WIn2000, my app, IB and IBO - the same as XPPro
NT4/SP6, my app, Paradox files - works fine
NT4/SP6, my app, IB and IBO - seems to work OK .(still doing some stress tests but way better than XPPro or WIn2000)
I have gone through so many installs and uninstalls of software on different machines and still can't figure out where the problem might be. I am guessing that this is a session problem??. ANY guidance or tips would be hugely appreciated.
[Non-text portions of this message have been removed]