Hi!
I'm currently planing to seperate my Frames from the direct database accesses.
So i'm only working with TCustomDADataSet in a Control Modul, but the grids in my frames need at least a TDataSource instance, so i get into the following questions. What's the difference between your TOraDataSource and the native one? Are there any problems by accessing parameters over TCustomDADataSet Routines?
coding questions
There is no much difference between TOraDataSource and TDataSource. TOraDataSource is implemented for ODAC conception completeness. Both of them are fully compatible with each other, so you can use any type of these objects in your application. In future we are going to extend TOraDataSource functionality and improve its usability.
coding question part2
thx, for your fast reply...
my project used a timer component and a Smart Query instance for checking a fieldvalue in my db repeatly. but this seems to conflicts sometimes, so i would like to try the thread proterty of your components... how does this work?
did i have to wait in a routine for the results of such a query? if so than how?
my project used a timer component and a Smart Query instance for checking a fieldvalue in my db repeatly. but this seems to conflicts sometimes, so i would like to try the thread proterty of your components... how does this work?
did i have to wait in a routine for the results of such a query? if so than how?
anybody here who knows how to handle a sql query in a own thread in borland c++?
anybody here who knows how to handle a sql query in a own thread in borland c++?
There are several ways to use Query in multi-threaded environment, for example you can create Session and Query in your thread then set them up and use it as usual, also you can set DataSet.NonBlocking to true thus all SQL statements will run in isolated threads but you still need to wait till execution ends to get the result (you can control execution flow by DataSet.Executing function).
Pls. ask more definite questions in future.
Pls. ask more definite questions in future.