corrupt tps files

I have an application that updates a tps file on a network drive. When more
than one pc (all running windows xp) is updating the file they get a corrupt
file error and the file has to be rebuilt with tpsfix. The caching is turned
off on all drives. Has anyone had a similar experience or know how to fix
this? The application has run fine at 30 locations for several years under
windows 98.

Ron Wright
ronald.wright@chicagopolice.org

http://www.granitebear.com/network.htm

--
Best Regards,
Earl R Coker
ksasales AT machlink DOT com
kwiksys AT kwiksystems DOT net
www.kwiksystems.net
www.kwiksystems.com
www.kwiksystems.com/clarion.htm (BigTamer(tm) Templates)


"Ron Wright" <clayart@ameritech.net> wrote in message
news:cwQYc.9106$FV3.8801@newssvr17.news.prodigy.com...
: I have an application that updates a tps file on a network drive. When
more
: than one pc (all running windows xp) is updating the file they get a
corrupt
: file error and the file has to be rebuilt with tpsfix. The caching is
turned
: off on all drives. Has anyone had a similar experience or know how to fix
: this? The application has run fine at 30 locations for several years under
: windows 98.
:
: Ron Wright
: ronald.wright@chicagopolice.org

"Ron Wright" <clayart@ameritech.net> wrote in message
news:cwQYc.9106$FV3.8801@newssvr17.news.prodigy.com...
> I have an application that updates a tps file on a network drive. When
more
> than one pc (all running windows xp) is updating the file they get a
corrupt
> file error and the file has to be rebuilt with tpsfix. The caching is
turned
> off on all drives. Has anyone had a similar experience or know how to fix
> this? The application has run fine at 30 locations for several years under
> windows 98.
>
> Ron Wright
> ronald.wright@chicagopolice.org

I have similar problem month ago, follow this link (if error you got is
1447)

FAQ'd
Clarionfoundry ->DataBase ->Drivers ->Topspeed ->Error 1477
Info on this exe: http://www.support.tabs3.com/main/r10104.htm

TPS doesn't do record locking very well. Turn off client write caching and
you'll be better off.

-- ken

Ron Wright wrote:

> I have an application that updates a tps file on a network drive. When mor
e
> than one pc (all running windows xp) is updating the file they get a corru
pt
> file error and the file has to be rebuilt with tpsfix. The caching is turn
ed
> off on all drives. Has anyone had a similar experience or know how to fix
> this? The application has run fine at 30 locations for several years under
> windows 98.
>
> Ron Wright
> ronald.wright@chicagopolice.org

Xref: newsfeed-west.nntpserver.com comp.lang.clarion:150450

TPS doesn't do record locking very well. Turn off client write caching and
you'll be better off.

-- ken

Ron Wright wrote:

> I have an application that updates a tps file on a network drive. When mor
e
> than one pc (all running windows xp) is updating the file they get a corru
pt
> file error and the file has to be rebuilt with tpsfix. The caching is turn
ed
> off on all drives. Has anyone had a similar experience or know how to fix
> this? The application has run fine at 30 locations for several years under
> windows 98.
>
> Ron Wright
> ronald.wright@chicagopolice.org

Sorry Ron;

I didn't mean to sound accusatory. This is just a sore topic with me. I
have experienced exactly what you describe more times than I want to
remember. And you are among good company when you rant about the larger
organizations not wanting to shore up their networks.

Somewhere, before accessing any files, try the following:
SEND(SomeFileName, 'TCF=' & CLIP(TCFPath) & '\SomeTCFFile.TCF') !
where TCFPath is defined by your application

This only has to be called once, and can be to any file. This call is
actually to the driver, and the file name does not matter, other than it has
to be defined, and using the driver you are attempting to set the TCF
location on. Your only requirement is that the call is made to each type of
driver needed (TOPSPEED,FOXPRO,etc.). Also, it must be done in ANY *.exe
running against your server files, in other words, on all workstations, and
applications that could be running concurrently on the same server based
files.

Hope this helps...

"Ron Wright" <clayart@ameritech.net> wrote in message
news:hyo4d.11858$kk.9230@newssvr31.news.prodigy.com...
>I AM NOT BLAMING THE DRIVER.
> The networks that this app is running on are indeed crap. I have no
> control
> over them. They are not going to change anything on the network to fix
> this.
> I have to make it work at my end. The problem is that they are upgrading
> some offices to XP and will not allow us to turn off the disk caching. I
> only have this problem with the XP machines. I runs fine on The 98
> machines.
> I am looking for help. I think that specifing that the TCF file be located
> on the server would fix the problem, but I don't know how to code this.
> The
> manuals are very unclear on how to do this.  Any help would be greatly
> appreciated. I am using 6.1 Enterprise. The app is run locally and
> accesses
> the file on a local server. That's 125 users and 30 servers. I am doing
> battle with a large organization here.
>
> Ron Wright  ronald.wright@chicagopolice.org
>
>
> Ron G. Rusk wrote: 

Ken McLeod <kmcleod@despammed.com> wrote in message news:<4149FAF3.8CFDB531@despammed.com>.
.
> TPS doesn't do record locking very well. Turn off client write caching and
> you'll be better off.
>
> -- ken

Hi Ken,

Can you enlighten us how this can be done?

> Ron Wright wrote:
> 

Sorry Ron;

I didn't mean to sound accusatory. This is just a sore topic with me. I
have experienced exactly what you describe more times than I want to
remember. And you are among good company when you rant about the larger
organizations not wanting to shore up their networks.

Somewhere, before accessing any files, try the following:
SEND(SomeFileName, 'TCF=' & CLIP(TCFPath) & '\SomeTCFFile.TCF') !
where TCFPath is defined by your application

This only has to be called once, and can be to any file. This call is
actually to the driver, and the file name does not matter, other than it has
to be defined, and using the driver you are attempting to set the TCF
location on. Your only requirement is that the call is made to each type of
driver needed (TOPSPEED,FOXPRO,etc.). Also, it must be done in ANY *.exe
running against your server files, in other words, on all workstations, and
applications that could be running concurrently on the same server based
files.

Hope this helps...

"Ron Wright" <clayart@ameritech.net> wrote in message
news:hyo4d.11858$kk.9230@newssvr31.news.prodigy.com...
>I AM NOT BLAMING THE DRIVER.
> The networks that this app is running on are indeed crap. I have no
> control
> over them. They are not going to change anything on the network to fix
> this.
> I have to make it work at my end. The problem is that they are upgrading
> some offices to XP and will not allow us to turn off the disk caching. I
> only have this problem with the XP machines. I runs fine on The 98
> machines.
> I am looking for help. I think that specifing that the TCF file be located
> on the server would fix the problem, but I don't know how to code this.
> The
> manuals are very unclear on how to do this.  Any help would be greatly
> appreciated. I am using 6.1 Enterprise. The app is run locally and
> accesses
> the file on a local server. That's 125 users and 30 servers. I am doing
> battle with a large organization here.
>
> Ron Wright  ronald.wright@chicagopolice.org
>
>
> Ron G. Rusk wrote: 

Hi Ron,

Our application software was using Clarion file driver and had been
running at customer sites for more than ten years without much
problem. The corrupted files problem pops up once we converted it to
use TPS file driver at the beginning of last year. It's a nightmare
for us and your advise gives us ray of hope.

We've put the statement into our application accordingly. Is the TCF
supposed to be hidden because the file (we name it to be TPSTX.TCF)
cannot be seen in the path (we put it in the server same as other
shared datafiles) before/after the LOGOUT nor COMMIT statement?

"Ron G. Rusk" <ron_rusk@charter.net> wrote in message news:<2ru345F1co7cfU1@uni-berlin.de>.
.
> Sorry Ron;
>
>     I didn't mean to sound accusatory. This is just a sore topic with me. 
I
> have experienced exactly what you describe more times than I want to
> remember. And you are among good company when you rant about the larger
> organizations not wanting to shore up their networks.
>
>     Somewhere, before accessing any files, try the following:
>        SEND(SomeFileName, 'TCF=' & CLIP(TCFPath) & '\SomeTCFFile.TCF') !
> where TCFPath is defined by your application
>
>     This only has to be called once, and can be to any file. This call is
> actually to the driver, and the file name does not matter, other than it h
as
> to be defined, and using the driver you are attempting to set the TCF
> location on. Your only requirement is that the call is made to each type o
f
> driver needed (TOPSPEED,FOXPRO,etc.). Also, it must be done in ANY *.exe
> running against your server files, in other words, on all workstations, an
d
> applications that could be running concurrently on the same server based
> files.
>
>     Hope this helps...
>