Migrating CfD 2.1 to CW 
Author Message
 Migrating CfD 2.1 to CW

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



Thu, 23 Dec 1999 03:00:00 GMT  
 Migrating CfD 2.1 to CW

Quote:


> >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!

regards
chris

- Show quoted text -

Quote:
> 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



Thu, 23 Dec 1999 03:00:00 GMT  
 Migrating CfD 2.1 to CW

Quote:

>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
sm
-----------------------------------------------------------------------
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



Fri, 24 Dec 1999 03:00:00 GMT  
 Migrating CfD 2.1 to CW

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



Fri, 24 Dec 1999 03:00:00 GMT  
 Migrating CfD 2.1 to CW

Quote:



>> >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!

Hi Chris

Clarion DAT driver 2.002 and prior versions of CW  were doing caching
all the time .. can lead to data corruption problems.

Best Regards
sm
------------------------------------------------------------------
Steve MacLeod        



Fri, 24 Dec 1999 03:00:00 GMT  
 Migrating CfD 2.1 to CW

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

Quote:
> 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



Fri, 24 Dec 1999 03:00:00 GMT  
 Migrating CfD 2.1 to CW

You can provide a batch file to run CSRT without user intervention.
Otherwise- removing the key files will suffice.  The only advantage to
using the sorter is that it will remove any deleted records.
--
Russell B. Eggen
Topspeed Consulting & Education

[Using MS Internet News 3.0]



Quote:
> 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



Sat, 25 Dec 1999 03:00:00 GMT  
 
 [ 7 post ] 

 Relevant Pages 

1. Converting Clarion DOS 2.1 *.DAT to CW - Choosing between CW VB Delphi

2. Migrate Clarion 2.1 Databases?

3. CFD 2.1 and Windows 98 with Novell 3.12

4. CFD 2.1/Win95 & End Task

5. CFD 2.1, Win2000, error 36

6. CFD 2.1 files

7. CFD 2.1 and Windows NT

8. CFD 2.1 and third party data files

9. Data File corruption in CFD 2.1

10. CFD 2.1, Windows 3.1, and Memory Problems

11. Error 36 in CFD 2.1 and Win95

12. CFD 2.1, CFIL, and WINFRAME

 

 
Powered by phpBB® Forum Software