TPS file system rewrites WRONG record 
Author Message
 TPS file system rewrites WRONG record

A record was created in file by C4b template code. The record was
autonumbered. During the same window/update time period data was
changed and when the record was rewritten it was written over a
previously entered old record. The old record happened to be
autoincremented
record NUMBER ONE. The first record in the file. Database is on NT
server
with WIN95/98 users.

This looks like an out and out failure of the TPS file system to
overwrite the
correct record.

Here are some fields and visual picture of what happened.

OLD RECORD                                              NEW RECORD
BEFORE the failure of TPS file system             AFTER

Auto increment Sysid:  1                                   11,266
Letterid:                       31                                 50
PersonID:                    49,846                          58,394
FileID:                         33,964
33,964    *same as old
AddressID:                  51,717                          65,444
Created  Date:             2-8-99                          2-8-99
*same as old
Time:                           12:51pm                       12:51pm
*same as old
Last Modified:             2-8-99                          12-7-99
Time:                          12:51pm                        3:25pm

This is only a partial list of fields, there were others that were same
as old.

Record 11,266 was the next sequential record added in the time period
indicated in the "Last modified" fields. When the PUT occurred record
number ONE was overwritten with SOME of the fields from
record number 11,266. Record number ONE ceased to exist. 11,266
appeared at the TOP of the TPS file when viewed in record number
order, followed by records 2,3,4,5,6...., etc.

The fileid pointer was correct for record number 1 and wrong
for record number 11,266.

Pretty scary to depend on a system that does this.

How does one figure out how to prevent this in the future?

Or do I just ignore it and try to get involved with more accurate and
reliable and compuer/development systems? If any exist on WIN.

---

Computer Systems Development, Inc.
Baltimore, MD. 21214  USA
410-254-7060



Mon, 03 Jun 2002 03:00:00 GMT  
 TPS file system rewrites WRONG record
Mike,

Could it be that you are doing some (conditional) file I/O
in one of your embeds which could disturb the record-position?

--
Best regards,
Maarten
C5EEb - ABC
Certainly Clarion Developer



Mon, 03 Jun 2002 03:00:00 GMT  
 TPS file system rewrites WRONG record
Check that there is no embed code which uses a SET or GET command for that
file in that window/update time period.

Stephen Fulton.


Quote:
> A record was created in file by C4b template code. The record was
> autonumbered. During the same window/update time period data was
> changed and when the record was rewritten it was written over a
> previously entered old record. The old record happened to be
> autoincremented
> record NUMBER ONE. The first record in the file. Database is on NT
> server
> with WIN95/98 users.

> This looks like an out and out failure of the TPS file system to
> overwrite the
> correct record.

> Here are some fields and visual picture of what happened.

> OLD RECORD                                              NEW RECORD
> BEFORE the failure of TPS file system             AFTER

> Auto increment Sysid:  1                                   11,266
> Letterid:                       31                                 50
> PersonID:                    49,846                          58,394
> FileID:                         33,964
> 33,964    *same as old
> AddressID:                  51,717                          65,444
> Created  Date:             2-8-99                          2-8-99
> *same as old
> Time:                           12:51pm                       12:51pm
> *same as old
> Last Modified:             2-8-99                          12-7-99
> Time:                          12:51pm                        3:25pm

> This is only a partial list of fields, there were others that were same
> as old.

> Record 11,266 was the next sequential record added in the time period
> indicated in the "Last modified" fields. When the PUT occurred record
> number ONE was overwritten with SOME of the fields from
> record number 11,266. Record number ONE ceased to exist. 11,266
> appeared at the TOP of the TPS file when viewed in record number
> order, followed by records 2,3,4,5,6...., etc.

> The fileid pointer was correct for record number 1 and wrong
> for record number 11,266.

> Pretty scary to depend on a system that does this.

> How does one figure out how to prevent this in the future?

> Or do I just ignore it and try to get involved with more accurate and
> reliable and compuer/development systems? If any exist on WIN.

> ---

> Computer Systems Development, Inc.
> Baltimore, MD. 21214  USA
> 410-254-7060



Tue, 04 Jun 2002 03:00:00 GMT  
 TPS file system rewrites WRONG record
Stock off the shelf Clarion C4B templates.

I used 3 embed points that have ENABLE/HIDE commands.
And a ForceRefresh and RefreshWindow.

7 lines total of these commands and that's IT, the rest is stock Clarion
template code.

There is not reasonable explanation other then memory failure or major
screwup when TPS file system was writting record.

Quote:

> Check that there is no embed code which uses a SET or GET command for that
> file in that window/update time period.

> Stephen Fulton.



> > A record was created in file by C4b template code. The record was
> > autonumbered. During the same window/update time period data was
> > changed and when the record was rewritten it was written over a
> > previously entered old record. The old record happened to be
> > autoincremented
> > record NUMBER ONE. The first record in the file. Database is on NT
> > server
> > with WIN95/98 users.

> > This looks like an out and out failure of the TPS file system to
> > overwrite the
> > correct record.

> > Here are some fields and visual picture of what happened.

> > OLD RECORD                                              NEW RECORD
> > BEFORE the failure of TPS file system             AFTER

> > Auto increment Sysid:  1                                   11,266
> > Letterid:                       31                                 50
> > PersonID:                    49,846                          58,394
> > FileID:                         33,964
> > 33,964    *same as old
> > AddressID:                  51,717                          65,444
> > Created  Date:             2-8-99                          2-8-99
> > *same as old
> > Time:                           12:51pm                       12:51pm
> > *same as old
> > Last Modified:             2-8-99                          12-7-99
> > Time:                          12:51pm                        3:25pm

> > This is only a partial list of fields, there were others that were same
> > as old.

> > Record 11,266 was the next sequential record added in the time period
> > indicated in the "Last modified" fields. When the PUT occurred record
> > number ONE was overwritten with SOME of the fields from
> > record number 11,266. Record number ONE ceased to exist. 11,266
> > appeared at the TOP of the TPS file when viewed in record number
> > order, followed by records 2,3,4,5,6...., etc.

> > The fileid pointer was correct for record number 1 and wrong
> > for record number 11,266.

> > Pretty scary to depend on a system that does this.

> > How does one figure out how to prevent this in the future?

> > Or do I just ignore it and try to get involved with more accurate and
> > reliable and compuer/development systems? If any exist on WIN.

> > ---

> > Computer Systems Development, Inc.
> > Baltimore, MD. 21214  USA
> > 410-254-7060

--
---

Computer Systems Development, Inc.
Baltimore, MD. 21214  USA
410-254-7060



Tue, 04 Jun 2002 03:00:00 GMT  
 TPS file system rewrites WRONG record
Remove the RefreshWindow and ForceRefresh and try again.
My suspicion is that on refresh the record is reset to the first record in
the file.
(Sorry, I'm only guessing here...)
If you want, and the app&dct is less than 1MB then email it to me and I'll
have a look at it.

If it is too large you may want to only email the dct, browse and update.

Stephen Fulton.


Quote:
> Stock off the shelf Clarion C4B templates.

> I used 3 embed points that have ENABLE/HIDE commands.
> And a ForceRefresh and RefreshWindow.

> 7 lines total of these commands and that's IT, the rest is stock Clarion
> template code.

> There is not reasonable explanation other then memory failure or major
> screwup when TPS file system was writting record.


> > Check that there is no embed code which uses a SET or GET command for
that
> > file in that window/update time period.

> > Stephen Fulton.



> > > A record was created in file by C4b template code. The record was
> > > autonumbered. During the same window/update time period data was
> > > changed and when the record was rewritten it was written over a
> > > previously entered old record. The old record happened to be
> > > autoincremented
> > > record NUMBER ONE. The first record in the file. Database is on NT
> > > server
> > > with WIN95/98 users.

> > > This looks like an out and out failure of the TPS file system to
> > > overwrite the
> > > correct record.

> > > Here are some fields and visual picture of what happened.

> > > OLD RECORD                                              NEW RECORD
> > > BEFORE the failure of TPS file system             AFTER

> > > Auto increment Sysid:  1                                   11,266
> > > Letterid:                       31                                 50
> > > PersonID:                    49,846                          58,394
> > > FileID:                         33,964
> > > 33,964    *same as old
> > > AddressID:                  51,717                          65,444
> > > Created  Date:             2-8-99                          2-8-99
> > > *same as old
> > > Time:                           12:51pm                       12:51pm
> > > *same as old
> > > Last Modified:             2-8-99                          12-7-99
> > > Time:                          12:51pm                        3:25pm

> > > This is only a partial list of fields, there were others that were
same
> > > as old.

> > > Record 11,266 was the next sequential record added in the time period
> > > indicated in the "Last modified" fields. When the PUT occurred record
> > > number ONE was overwritten with SOME of the fields from
> > > record number 11,266. Record number ONE ceased to exist. 11,266
> > > appeared at the TOP of the TPS file when viewed in record number
> > > order, followed by records 2,3,4,5,6...., etc.

> > > The fileid pointer was correct for record number 1 and wrong
> > > for record number 11,266.

> > > Pretty scary to depend on a system that does this.

> > > How does one figure out how to prevent this in the future?

> > > Or do I just ignore it and try to get involved with more accurate and
> > > reliable and compuer/development systems? If any exist on WIN.

> > > ---

> > > Computer Systems Development, Inc.
> > > Baltimore, MD. 21214  USA
> > > 410-254-7060

> --
> ---

> Computer Systems Development, Inc.
> Baltimore, MD. 21214  USA
> 410-254-7060



Fri, 07 Jun 2002 03:00:00 GMT  
 
 [ 5 post ] 

 Relevant Pages 

1. number of records for tps file and searching files

2. copy records from old tps to new tps

3. Copying Records from a Queue to a TPS file

4. Number of Records in a TPS file

5. TPS File System

6. Looking for TPS file W/O TPS Estention

7. TPS file recovery utility/TPS ODBC problem

8. Aucocobol/Vision file system, reading a deleted record.

9. Grabbing Wrong Field, Wrong File

10. Rewriting data using REWRITE ?

11. Converting data from TPS table to MS SQL 7 table getting wrong values

12. HELP: Intro book on Rewriting Systems

 

 
Powered by phpBB® Forum Software