Moving from Clarion .tps to SQL

[reillypainting]

We have been having problems with database corruption in our Clarion system. Our programmer has been suggesting that moving our current .tps database from our shared file server to a dedicated SQL server will solve these problems. Any thoughts?

 

[ShankarJ]

Hi!

ISAM data files (like Topspeed) are always suspect to corruptions on a Microsoft network. Disabling Opportunistic Locking (OpLocks) and caching on the server & workstations does reduce the problem but it is NEVER a permanent trouble-free solution. Also, some have had good success by hosting the database on a Linux server with SAMBA.

The transition from TPS to SQL will offer a lot of GOOD dividends like no database corruptions, faster access to data, processes & reports can be optimized to have the server do most of the work using SQL queries or Stored procedures, etc.

In short, the transition from TPS to SQL is the BEST option keeping the future in mind.

Incidentally, CGF is having a 50% special on their DMC product which can drastically reduce the time required to convert your TPS dictionary/application to a SQL one (

http://www.dmc-fr.com/boutique_en.php).

Regards