Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
SQL Server 2008 table as a record source
Message
From
21/02/2016 04:51:30
 
 
To
20/02/2016 18:46:17
Dragan Nedeljkovich (Online)
Now officially retired
Zrenjanin, Serbia
General information
Forum:
Visual FoxPro
Category:
Databases,Tables, Views, Indexing and SQL syntax
Environment versions
Visual FoxPro:
VFP 9 SP2
OS:
Windows 8.1
Network:
Windows 2008 Server
Database:
MS SQL Server
Application:
Desktop
Miscellaneous
Thread ID:
01620689
Message ID:
01631795
Views:
55
>>>>Backend you were working against? .WhereType you are using ? Which PK-Type and (depending on previous answers) how created ?
>>>
>>>SQL /(20005 and 2014, possibly 2008r2 as well), pk only, int, created manually (i.e. calling a server-side function independently, before tableupdate).
>>
>>Conflict strategy / .WhereType you are using ?
>>
>>As this is some kind of tree/recursive table, 1st CA probably needs to tableupdate() for an error to manifest at all, but nothing written above or necessary about 2nd CA. "Same record" of 3rd CA refers to newly created record from 1st CA, last from 2nd (implying tableupdate() there, all "new" records or some greater set?
>>
>>We have sometimes summary CA working on R/W tables, we have recursive tables for instance for rights, often used in security joins/filters, but probably not your scenario.
>
>OK, more details. This is two tables with persons in them; the first one contains candidates (coming from the web, so it may contain spam). This happens when a candidate is approved, its record is inserted into the people table. The 2nd bizobject is in charge of inserting the phone into the phones table and updating a FK field in the people table, then it tableupdates both (phones and people). The 3rd bizobject then just retrieves this record as if it would retrieve any other people record, for display.
>
>While I was doing the safe select into this 3rd bizobject's CA (i.e. senduptates=.f., zap, select into a temp cursor, append from it, all of a sudden the .sendupdates=.t. and this append is now an insert, immediately sent to server, key constraint violation, bang. Tried to work around this in several ways, and in the end only .cursorfill with a new .selectCmd worked.

sql session is the same ?
check sql traffic with sql profile.
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform