6.53 is a recompiled version of 6.52 that is prepared to run with Windows 7 x86 and x64.
It has not been improved or bug fixed in any functional way to retain 100% comaptibillity with DataEase for Windows 6.52. On the other hand, we have made it look contemporary with a "livery" borrowed from the latest DataEase for windows and inspired by DataEase Generation 3. Multi User and Multi Session setup in Legacy versions of DataEease is and was never as simple as it should have been. We have to admit that it was very tempting to "sort" this out in 6.53, but in the end we kept to the scope and left it as it is.
In 6.52 you have to re-install the software to change the Network Setting, but if you choose anything but "None" on locking model, 6.52 will not work until you have configured the network setting manually.
In our mind, this is not a good way of starting off so we ALWAYS install 6.53 with Single User settings, and then you can set up and change the Locking model yourself manually later.
In the Program catalogue of 6.53 you will find a catalog called NetworkAndLocking. In this catalogue you will find 4 catalogue named after thir locking model. In each you will find the correct CONFIGUR.DAT for this locking model.
The only thing you have to do to set or change your locking model, is to copy the correct CONFIGUR.DAT to the Shared catalogue you need to run 6.53 in a multi user/multi session environmen.
NB! Remember to delete the configur.dat in the DataEase program catalogue (ex, c:\dataease65.local) if not it will take precedence and stop you networking setup from working.
The shared catalogue.
If you want to run 6.53 as multi session with locking, create a new catalogue on the root of your C:\ drive called ex. C:\653locking, copy denetwrk.ovl from the 653 program catalogue, and the configur.dat with the correct locking model setting from the NetworkAndLocking catalogue. Make sure that you also copy it to the program catalogue, as the one in the shared catalogue and in the program catalogue need to be the same. (You can also delete configur.dat in the program catalogue)
If you want to run multi session, you will need each session to have an unique DENAME. So make a bat file for each session, and start if from a shortcut. The bat files should atleast contain the belowe:
SET DENAME=Something UniqueForEachSession
SET DEPATH=C:\SharedCatalogue ex. C:\652locking
If you want to run the application in a multiuser environement, you will need to put the Shared catalogue on a shared Network Drive together with the Shared application. You will still need a unique DENAME for each user and each session.
With every new version of Microsoft Windows, there is new opportunities, new solutions, new problems and new challenges. ODBC has been around for more than 20 years now, and it is has always been a popular way to quickly access data in different databases...
False Virus Detection in 6.53: Resolved!
Soon after the release of 6.53 we started to get reports from our customers that the software wouldn't install properly.
After some investigation, we found out that it installed properly but some of the system files was identified as "possible" viruses...
DataEase - Migration and Upgrade Path.
DataEase is currently undergoing a big transition. Since 1995 with the release of DataEase for Windows (5) every version has more or less been an increment of this product. In Version 5 every new version was simply a bug fix. In 6 the news was OML, Webpub...
Wait for Eight! - DataEase 8, not the other one...
We know that a lot of DataEase 6.x users, have tried migrating to DataEase 7.x, and for variable reasons this has not been a success. In the early days (7.0 and 7.1) the problem was that 7.x was still a immature product, and later when things stabilized i...