> >Hi all,

> >some time ago TopSpeed indicated that the CfD batch# 2110 DAT & key files were
> >compatible with the CW Clarion driver.  All that was required was a recompile of
> >APPs and CSRTing the DAT files to rebuild the keys.

> >Since we have over 120 branches transmitting orders in the form of DAT & Key files,
> >the CSRT part would become a bit of a nightmare to schedule.  Would the same result
> >be achieved with a recompile of the APPs and deleting all keys files, thus forcing
> >the recompiled APP to build the DAT file?

> >I need an authorative answer on this please TopSpeed.

> >Thanks chaps

> >Mike

> Hmm, should be no csrt step required at all .. CPD 2.110 and CW 2.003
> Clarion driver is supposed to be 100% compatible. Should be no trouble
> having a CW app and a CPD 2.110 app share the same data files.

> hth

> Best Regards -----------------------------------------------------------------------
> Steve MacLeod        Microcomputer Specialist           (902)563-1625
> Computer Centre      University College of Cape Breton
> Sydney, N.S.         Canada                              B1P 6L2

>          --------------------ooOOoo---------------------

> http://w3.uccb.ns.ca/clarion         Team TopSpeed Internet

>Hi all,
>some time ago TopSpeed indicated that the CfD batch# 2110 DAT & key files were
>compatible with the CW Clarion driver.  All that was required was a recompile of
>APPs and CSRTing the DAT files to rebuild the keys.
>Since we have over 120 branches transmitting orders in the form of DAT & Key files,
>the CSRT part would become a bit of a nightmare to schedule.  Would the same result
>be achieved with a recompile of the APPs and deleting all keys files, thus forcing
>the recompiled APP to build the DAT file?
>I need an authorative answer on this please TopSpeed.
>Thanks chaps
>Mike

>> >Hi all,

>> >some time ago TopSpeed indicated that the CfD batch# 2110 DAT & key files were
>> >compatible with the CW Clarion driver.  All that was required was a recompile of
>> >APPs and CSRTing the DAT files to rebuild the keys.

>> >Since we have over 120 branches transmitting orders in the form of DAT & Key files,
>> >the CSRT part would become a bit of a nightmare to schedule.  Would the same result
>> >be achieved with a recompile of the APPs and deleting all keys files, thus forcing
>> >the recompiled APP to build the DAT file?

>> >I need an authorative answer on this please TopSpeed.

>> >Thanks chaps

>> >Mike

>> Hmm, should be no csrt step required at all .. CPD 2.110 and CW 2.003
>> Clarion driver is supposed to be 100% compatible. Should be no trouble
>> having a CW app and a CPD 2.110 app share the same data files.

>> hth

>Hi Steve,
>I use CW and CPD 2.1 together on the same .DAT files.  So far no
>problem, but I am very nervous.  There are differences, according to
>Topspeed.  I never used CSRT.  Also, after trying the 2003 driver I
>reverted back to 2002.  The performance of 2002 was better.  But is
>there a bug that 2003 tried to cure?  I think so, but I don't know how
>serious it was.  Maybe I am at risk!

> Mike,

> FWIW, I didn't run CSRT on any of my DAT files when I converted to CW
> and yet the new versions worked 100% correctly (well maybe a few bugs
> which were mine!! <VBG>).

> HTH

> Al

> Which batch# did you migrate from? If it was 2110, then you shouldn't
have had a
> problem.  

> We are migrating from 2107 to 2110 & then to CW.  2107 key structures are
> incompatible with CW structures.  Hence the need to migrate from 2107 to
2110 first
> by recompiling and rebuilding key files via CSRT.

> Since we have many remote sites connecting daily, we can transmit the new
EXE
> electronically, and ideally rebuild the remote key files via

> DEL *.K*
> APP.EXE which would then rebuild the *.K* files in the appropriate
format.

> If not, running CSRT on each site would prove quite an exercise.

> Regards

> Mike