Re: Help on resolving record conflicts with ADO

I misunderstood your note about adding a resync command. I was picturing
the following:

dataset.resync([]);

And I just couldn't figure out how it would be helpful. I didn't realize
you meant use the resync_command in TBetterADO or rather ['Resync Command']
in TADO. I set up TBetterADO with my select statement in the resync_command
and it works great.

Thanks for your input.

"Brian Bushay TeamB" <BBushay@xxxxxxxxx> wrote in message
news:pcg702tmhaneq6j8degf8hromji85e9nqc@xxxxxxxxxx

A while ago it was suggested that I try this:

ADODataSet1.RecordSet.ReSync(adAffectCurrent, adResyncAllValues);
ADODataSet1.UpdateCursorPos;
ADODataSet1.Cancel;
Action := daAbort;

If my select statement is from 1 table, the above code works fine, but if
I
include any fields from another table through a left outer join (the other
table's field is for display purposes only) then the above code crashes
with
'Key value for this row was changed or deleted at the data store. The
local
row is now deleted.'. My select statement contains the primary key for
the
table I want to update, and only one field from the other table. I've
tried
BetterADO with no success. I'm wondering if the problem is how I'm
building
the select statement, but I don't see any other way to do what I need to
do.

SELECT table1.id, table1.name, table1.amount, table2.displayfield FROM
table1 LEFT OUTER JOIN table2 ON table1.id = table2.
id
As I said in the last message you can not properly resysnc a Join without
writing a "Resync_command"

Also I can point out that what you are trying to do seems better suited to
using
a lookup field than to using an outer join
--
Brian Bushay (TeamB)
Bbushay@xxxxxxxxx


.

Relevant Pages

  • Re: Problem using SP as record source with Access2002 & SQL Server 7
    ... automatic primary key without using Unique Identifier? ... I have set the unique table property, but the Resync Command is empty. ... difference between the Record Source property and the Resync Command ... > tables (and preferably, single field primary key). ...
    (microsoft.public.access.adp.sqlserver)
  • Re: Problem using SP as record source with Access2002 & SQL Server 7
    ... Create another stored procedure with the same Select statement but with the ... This clause should only take into account ... the primary key and the stored procedure to have only one argument, ... > the Resync Command property refer to the Input Parameters property? ...
    (microsoft.public.access.adp.sqlserver)
  • "Unique Table" and "Resync Command" problems with self-ref query
    ... I am unable to use "Unique Table" and "Resync Command" ... properties with self-referencing queries in ADO 2.8. ... FROM EMPLOYEE LEFT OUTER JOIN EMPLOYEE AS E2 ON E2.employee = ... e2.employeename as supname FROM EMPLOYEE LEFT OUTER JOIN ...
    (microsoft.public.data.ado)
  • Re: Problem using SP as record source with Access2002 & SQL Server 7
    ... in the underlying record source ERROR Message' article. ... the Resync Command property refer to the Input Parameters property? ... the GUID should only be used in association with ... >> an automatic primary key without using Unique Identifier? ...
    (microsoft.public.access.adp.sqlserver)