And is normal that this kind of instructions (like SQLSelect) to be called in literally hundred of methods and several times in each method, is a gargantuan task don't made this synchronous. I think that this is the usual behavior of all databases API (like JDBC, ODBC....).
> > Some tasks (like database interactions) are predicated on normally > synchronous activity. > > Calling SQLSelect and at some point in the future getting results > makes writing a client server app much harder than it needs to be. > > I'd be willing to bet that anyone using a database depends on > SQLSelect behaving synchronously. > > _______________________________________________ > Unsubscribe or switch delivery mode: > <http://www.realsoftware.com/support/listmanager/> > > Search the archives: > <http://support.realsoftware.com/listarchives/lists.html> > _______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives: <http://support.realsoftware.com/listarchives/lists.html>
