I have a great problem:
    I have a Query that recover many rows from a Informix Table.
    This  Query have linked a TDataSource that have his property
AutoEdit to True.
    When I change information from any of the rows, and came with a
DBNavigator to another row in the Query and I try to change this new row
I obtain this error message:
                    'Couldn't perform the edit because another user
changed the record.'

??    Realy no body change the record.  !!

    Seem to be a process that mark all the record in the table as
modified by another user.

    I tryed to do all that I now on Delphi 3. I think that the problem
is in the Informix Server.

        PLEASE, PLEASE, PLEASE... Can anyone help me to kill to the user
"another"?

        It's urgent. I can pay for a good response, but
rapidly.            Thank's in advance.

        Juan CCill.             Electronic Bussines System. Madrid
Spain.

I have a great problem:
    I have a Query that recover many rows from a Informix Table.
    This  Query have linked a TDataSource that have his property
AutoEdit to True.
    When I change information from any of the rows, and came with a
DBNavigator to another row in the Query and I try to change this new row
I obtain this error message:
                    'Couldn't perform the edit because another user
changed the record.'

??    Realy no body change the record.  !!

    Seem to be a process that mark all the record in the table as
modified by another user.

    I tryed to do all that I now on Delphi 3. I think that the problem
is in the Informix Server.

        PLEASE, PLEASE, PLEASE... Can anyone help me to kill to the user
"another"?

        It's urgent. I can pay for a good response, but
rapidly.            Thank's in advance.

        Juan CCill.             Electronic Bussines System. Madrid
Spain.

In article <35804AD1.7F09C...@databasedm.es>,
  "Juan CCill." <jcilleru...@databasedm.es> wrote:

I think the problem is in the isolation level;
you must set the isolation to committed read in the TDatabase
or Execute "set isolation to read committed" in the formcreate event.

If that doesn't work lower again the isolation level to dirty read.

My last and best advice (though you would have to do some coding)
is to USE CACHED UPDATES. That's right.
Use that and your problem will go away.

Zandy,

IT-JTM Systems
Philippines

-----== Posted via Deja News, The Leader in Internet Discussion ==-----
http://www.dejanews.com/   Now offering spam-free web-based newsreading