Insufficient base table information for updating or refreshing


10-Oct-2016 08:04

I am using Delphi 6 with ADO components and SQL Anywhere 8.02. If you change your cursor location to be server, that should work around the problem.

On a form, i put a TADOConnection who use Asa Prov. I put a DBGrid for viewing the datas of my table I modify datas and when i post the modifications, i have the following error message : "INSUFFICIENT BASE TABLE INFORMATION FOR UPDATING OR REFRESHING" I have read a lot of messages in groups and forums and i have not found a solution : it's not a problem of primary key, not a problem of multiple tables query... (Change the ADOTable or ADOQuery Cursor Location to cl Use Server).

Insufficient Base Table Information For Updating Or Refreshing 3.

Insufficient base table information for updating or refreshing 4.

On a form, i put a TADOConnection who use Asa Prov. I put a DBGrid for viewing the datas of my table I modify datas and when i post the modifications, i have the following error message : "INSUFFICIENT BASE TABLE INFORMATION FOR UPDATING OR REFRESHING" I have read a lot of messages in groups and forums and i have not found a solution : it's not a problem of primary key, not a problem of multiple tables query... :-\ Thanks in..."Before Update" and "After Update Of" triggers Hi all, In a row-level before update trigger I set the value of a column ("Some Column) to some value (the value is only changed by this trigger, not by the update statement itself) Now I notice that the row-level trigger defined as "after update of Some Column" doesn't fire when I change the value of this column in the before update trigger.

It does fire (as expected) when the change comes from the update statement itself) Questions: - Is this expected behaviour? Proposal: Rename "software update" to "application update"Rumor has it that lots of extension update bugs get filed in the "software update" component when they should be filed in the "extension/theme manager" component.

The basetablename and basecolumnname properties reside within the field properties and this message often occurs when the values are Null. (adoanywhere browser exposes these properties but you can do the same in code if you have time). -- Mike Collier BSc (Hons) - Object Browser and COM Server.

In your case ,the server didt know which record to update?? I spent some more time on it and eventually discovered that I had the following line in my global code module: - Conn Main. This is a problem with client side cursors and was fixed recently in 8.0.2.4076 and 8.0.1.3062 EBFs.