Going to check that but I don't believe so.
Found that if I force the update, it works.
Michael Oke, II
661-349-6221
Contents of this and all messages are intended for their designated recipient.
On Aug 8, 2012, at 1:40 PM, MB Software Solutions,
On 8/7/2012 1:54 PM, Michael Oke, II wrote:
Except the same code, on a different but similar table, does not show the
same issue. It is the TableUpdate that throws this error and I'm just trying
to narrow down any possible causes.
Reserved name?
--
Mike Babcock, MCP
MB Software
Strange error happening. VFP 6 application using SQL server backed. We are
using remote views to access the data When attempting to save a record that
has a text field with special characters in it, such as [ ] square brackets, we
get an error: Update Conflict. Anyone have any ideas
in it, such as [ ] square
brackets, we get an error: Update Conflict. Anyone have any ideas as to
what to look at?
Michael Oke, II
661-349-6221
Contents of this and all messages are intended for their designated
recipient.
[excessive quoting removed by server
brackets,
we get an error: Update Conflict. Anyone have any ideas as to what to look at?
--
[] in MSSQL are containers in that it will contain spaces in a column
name tat came from Access. Or it will contain the slash used in an
instance [MyServer\theInstance] .dbName.dbo.[Stupid
attempting to save a record
that has a text field with special characters in it, such as [ ] square
brackets, we get an error: Update Conflict. Anyone have any ideas as to
what to look at?
Michael Oke, II
661-349-6221
Contents of this and all messages are intended for their designated
snip
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 :(
snip
Vince care
-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 getting an update
Wolfe, Stephen S YA-02 6 MDSS/SGSI wrote:
snip
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
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
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 low
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 some
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
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 table
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 low
.
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 update conflict
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 Computing,
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 view source code
18 matches
Mail list logo