Jeff, the only way I can think this is happening is if some combination
of factors is causing the APPEND command to run (unless you've got
INSERT commands around too) without the user realising this.
Does this application use a DBC? Maybe you could create a database
event that logs the data to a text file whenever a new record is added
and track any other data that might help you track it down. Maybe user
or machine name, date and time and if possible what program and line of
code it was called on.
Frank.
Frank Cazabon
On 22/02/2013 05:23 PM, Jeff Johnson wrote:
I also found out that 40 percent of their orders are phantom orders!
Over the last nine months the phantom orders are 50% of the orders on
the highest volume day and 18% on the lowest volume day. Sure points
to volume but why 40% overall! And most of them are in large blocks
of 20 to 60 orders in a row.
When appending records there is a stored procedure called
newid('order') that is set to the default value for the invoice
number. Most of their records are copied from a previous invoice.
scatter invoice to copy, append blank (which generates the new invoice
number using the stored procedure) gather some fields. After editing
the save does an sql update/set.
It was working fine until June of last year. They think they were
hacked but what could someone hack to cause this problem?
Thanks again for all your help.
Jeff
---------------
Jeff Johnson
[email protected]
(623) 582-0323
www.san-dc.com
www.arelationshipmanager.com
On 02/22/2013 02:03 PM, Kurt wrote:
Well - I guess you slashed One Phantom off your List! :-)
As for a Corrupt EXE - I doubt it. How could it be corrupt - such
that the
system Works - but, adds strange records. I suspect a truly corrupt EXE
would just Crash or Not work at all! I think the culprit is elsewhere...
-K-
-----Original Message-----
From: ProfoxTech [mailto:[email protected]] On Behalf Of Jeff
Johnson
Sent: Friday, February 22, 2013 2:31 PM
To: [email protected]
Subject: Re: Weird Problem Adding Records to a Table
Is there any chance at all that the executable could be corrupt? I
don't know if I mentioned it but on some days there could be 60 or 70
phantom records right in a row.
Update. The slash is merely a coincidence based on my test. The slash
has nothing to do with phantom records.
Jeff
---------------
Jeff Johnson
[email protected]
(623) 582-0323
www.san-dc.com
www.arelationshipmanager.com
On 02/22/2013 12:23 PM, MB Software Solutions, LLC wrote:
On 02/22/2013 07:33 AM, Kurt wrote:
My suggestion - KILL that Append/Gather - and replace that code with
an SQL
Insert! Its what I have done in the past in some problem areas of
systems -
and its done Wonders!!!
INSERT INTO MyTable FROM NAME if you've got objects to insert;
otherwise direct INSERT INTO MyTable (fields) VALUES (values) like he
said should fix it. I recall that from VFP5 days in late 90s.
[excessive quoting removed by server]
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/[email protected]
** All postings, unless explicitly stated otherwise, are the opinions of the
author, and do not constitute legal or medical advice. This statement is added
to the messages for those lawyers who are too stupid to see the obvious.
