Wolfe, Stephen S YA-02 6 MDSS/SGSI wrote:
>
>
>> The one that most often bites me is inadvertently changing a field
>> value, and then trying to move the record pointer without first
>>
> issuing
>
>> an update (and, sometimes, a requery()) Good luck - those messages
>> drive me mad
-9994
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of MB Software Solutions
Sent: Monday, April 16, 2007 11:14 AM
To: profox@leafe.com
Subject: Re: VFP8: Update Conflict
Wolfe, Stephen S YA-02 6 MDSS/SGSI wrote:
> What are the 'valid' reasons for
> The one that most often bites me is inadvertently changing a field
> value, and then trying to move the record pointer without first
issuing
> an update (and, sometimes, a requery()) Good luck - those messages
> drive me mad. I often give up and just rewrite it as a SPT :(
Vince care to e
EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of MB Software Solutions
Sent: Monday, April 16, 2007 2:19 PM
To: profox@leafe.com
Subject: Re: VFP8: Update Conflict
Rick Schummer wrote:
> Stephen,
>
> The conflicts are dependent on the settings for the view. Maybe if you
posted the vi
Rick Schummer wrote:
> Stephen,
>
> The conflicts are dependent on the settings for the view. Maybe if you posted
> the view source code
> (Show SQL in the View Designer). Another suggestion is to use the SQL
> Profiler to see what VFP is
> sending back to SQL Server.
>
> Rick
> White Light Compu
.
www.whitelightcomputing.com
www.rickschummer.com
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Wolfe, Stephen
S YA-02 6 MDSS/SGSI
Sent: Monday, April 16, 2007 10:44 AM
To: [EMAIL PROTECTED]
Subject: VFP8: Update Conflict
What are the 'valid' reasons for getting an updat
Wolfe, Stephen S YA-02 6 MDSS/SGSI wrote:
> What are the 'valid' reasons for getting an update conflict when you are
> using a remote view to a MSSQL table back end? The view carves out
> selected records and computed values from a single table. Activity on
> the table is typically very, very lo
On 4/16/07, Wolfe, Stephen S YA-02 6 MDSS/SGSI
<[EMAIL PROTECTED]> wrote:
> What are the 'valid' reasons for getting an update conflict when you are
> using a remote view to a MSSQL table back end? The view carves out
> selected records and computed values from a single table. Activity on
> the
> What are the 'valid' reasons for getting an update conflict when you are
> using a remote view to a MSSQL table back end? The view carves out
> selected records and computed values from a single table. Activity on
> the table is typically very, very low. Like maybe a few transactions
> per se
On 4/16/07, Wolfe, Stephen S YA-02 6 MDSS/SGSI
<[EMAIL PROTECTED]> wrote:
> What are the 'valid' reasons for getting an update conflict when you are
> using a remote view to a MSSQL table back end?
1. Someone else updated the data.
2. You're specifying the wrong records to update.
3. You've got s
Wolfe, Stephen S YA-02 6 MDSS/SGSI wrote:
> What are the 'valid' reasons for getting an update conflict when you are
> using a remote view to a MSSQL table back end? The view carves out
> selected records and computed values from a single table. Activity on
> the table is typically very, very lo
What are the 'valid' reasons for getting an update conflict when you are
using a remote view to a MSSQL table back end? The view carves out
selected records and computed values from a single table. Activity on
the table is typically very, very low. Like maybe a few transactions
per second would
12 matches
Mail list logo
