Hi!
    I think this has been asked many times...
    My problem is when I try to use a TQuery component with a Access97
database and set
    cachedupdates to True, i get this error message : ' General SQL error...
Operation not supported
    for this type of object.Field.' What does this mean?
    I tried with DBDEMOS and it works fine...
    If anyone can help me, i'll be very glad...
    Thanks in advance!
    I use D3 Standard Edition with BDE4.51.... My database is Access97

Try changing the update mode of the query to whereKeyOnly.

Juan

Sorry but i always use whereKeyOnly.... still doesn't work....
any other ideas?

Ok, compare the two tables/queries (DBDEMOS and yours) and see what's
different. That's all I can think of right now.

Thanks Juan! :)
I've got it.... If you use a VarChar field in your Access table, you can't
use cached updates....
I changed this field and it works fine....

Thanks for your patience :)

hi all -

i'm having the same problem that hdemir was having, but i wasn't able
to solve it by not using varchar fields.

here's the setup:

  - delphi c/s 3.02, bde 4.51, msaccess native driver using
    idda3532.dll
  - ms access 97, 2 tables in .mdb file: tblMilestone,
    tblMilestoneHistory (see below for data definition)
  - 2 query components, 2 updatesql components, master(tblMilestone)
    detail(tblMilestoneHistory) setup, cached updates true, update
    upWhereKeyOnly

when i execute the select statement "select * from tblMilestone" i
get the message "general sql error. operation is not supported for
this type of object. field."

what does this mean, and what can i do about it? i've got a deadline,
and this is driving me nuts.

thanks for your help,

- phil
_____________________________________________________________________
                                                        phil robinson
                                                   ph...@followup.com
                                        http://www.followup.com/phil/

data definition:

CREATE TABLE tblMilestone
(  MilestoneID          COUNTER          NOT NULL,
   MilestoneDate        DATE             NOT NULL,
   Description          CHAR(100)        NOT NULL,
   Completed            BIT              NOT NULL,

   CONSTRAINT MilestoneID PRIMARY KEY (MilestoneID)
);

CREATE INDEX MilestoneDate ON tblMilestone (MilestoneDate);
CREATE INDEX Description   ON tblMilestone (Description);
CREATE INDEX Completed     ON tblMilestone (Completed);

CREATE TABLE tblMilestoneHistory
(  HistoryID            COUNTER          NOT NULL,
   MilestoneID          LONG             NOT NULL,
   HistoryDate          DATE             NOT NULL,
   Comment              LONGTEXT         NOT NULL,

   CONSTRAINT HistoryID   PRIMARY KEY (HistoryID),
   CONSTRAINT MilestoneID FOREIGN KEY (MilestoneID)
                          REFERENCES tblMilestone (MilestoneID)
);

CREATE INDEX HistoryDate ON tblMilestoneHistory (HistoryDate);

In article <35255D40.9C3C...@followup.com>, Phil Robinson
<ph...@followup.com> writes

the problem was not the data type unfortunately.......
i recreated all database with Database Desktop and it's ok for now...
i think some datatypes aren't %100 compatible...