🚀 go-pugleaf

"Mike" <mike.powell@transcore.com> wrote:

I think I identified a possible problem of mine that prevented me from updating the record sets. Is it true that InterBase select stored procedures return a read only record set? If this is the case, then that would certainly explain what I was seeing.


>
>"Mike" <mike.powell@transcore.com> wrote:
>
>I think I have narrowed down the "problem" to TClientDataSet's inability to become aware of the server side schema (e.g. table defs, referential and check constraints, etc).
>
>I seem to remember there being a post or three on the topic of ensuring that the client does become aware of the schema information. Where is this post or where are the resources to achieve this measure?
>
>Thanks in advance.
>
>>
>>Ok, I need to backup a step or two.
>>
>>I am trying to make changes to a record set in a multitier database configuration. The changes seem to post on the first time out, but subsequent attempts fail with "ClientDataSet: Must apply updates before refreshing data." It doesn't matter what I do, the changes seem to get stuck in the client data set.
>>
>>My environment is Windows 2000, InterBase 6.0, C++Builder Enterprise. I am using the typical 3-tier configuration with an IBTransaction, IBDatabase, IBUpdateSQL, IBQuery, and IBDataSetProvider in the middle tier. The client uses a SocketConnection, a ClientDataSet, and a DataSource. I am feeding a simple DBGrid in conjunction with a DBNavigator.
>>
>>I have a sample project setup with both client and server if someone would care to take a look. I'd greatly appreciate it. Thanks.
>>
>