I am trying DataEase 6.53 in a network but don´t work. I copy the files configur.dat and denetwork.ovl for the FULL locking strategy but I have not any locking. I look in Preferences - Locking and I have a double mark in Lock nothing and Lock files in the section "If printing data is locked..."

Hi Carlos. Have you set the DEPATH correctly? The easiest way to do this is to start Dataease.exe via a bat file and include the DEPATH and DENAME in the bat file. Quote from our website "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 both your program catalogue, and the Shared catalogue you need to run 6.53 in a multi user/multi session environment. 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 C:\DataEase65.local\dataease.exe 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. Multi Session If you want to run more than one 6.53 at against the same database on a Local Computer, you need to set SharedLocalDatabase=Yes in the [Locking] section of PRISM.INI found in the DataEase program catalogue. You can alternatively map a local drive as a network drive and access the application via this drive."

I´am working with dataease since 1980 and before upgrade I need to be sure about the work of the "new" version But let me insist: After copy the configur.dat I look at Preferences - Locking and I have the double mark in Lock nothing and in Lock files options in the section "If printing data is locked...". If I try off one of them, the double mark pass at othe section. So in Networking I have not any locking.

Hi again Carloz. If your Locking screen doesn't show up with a Locking strategy, there is only to possible explainations: 1. That the configur.dat copied to the shared catalogue pointed to at the server by DEPATH environment variable, is the wrong one (i.e. it is the one for Single User) 2. That the DEPATH is not there or is not pointing on the correct catalogue. Where do you set your DEPATH? Is it in a bat file that later load DataEase.exe or is it in the outer environment (i.e. Windows etc). If you set it in Windows, simply run CMD and type SET, to check if it is set correctly. I know that you have been a DataEase user for "ages", but I do these mistakes dayly myself, so I assume that everyone else do to...Can't see the forrest for all the trees...

I did a new test: Windows server 2008, with the new DataEase 6.53 and Dataease 6.52 All stations via Terminal Server Depath and Dename via a .bat file with the configur.dat for the new version DataEase 6.52 it´s in the Denetwrk.ovl and all locks are OK DataEase 6.53 (LegEasy6 Demo version) it´s not in the Denetwrk.ovl and fail all locks.

Dear Carlos. I am very sorry, I didn't realise that you were trying to test this with the demo version. I thought you had a Network version. The demo version is set up to only run as a Single User. It is a demo of the functionality in DataEase for "new" users and as a "proof of concept" in Windows 7/8/2008R2. You don't need to test networking in 6.53. It is the same as in 6.52, so if it works in 6.52 it works in 6.53. We have tested it many, many times, so if you buy 6.53 and it doesn't work, you can be safe that it is a configuration issue, and not a systemic fault in the product. All Demo versions are single users, and even if you would need at least a two user full version to make a full scale Networking test. The problem with 6.53 in Windows 2008R2 is not related to running the product, but to the configuration of 2008R2 itself when it comes to locking etc. We have tested this extensively too, and with all default configurations of 2008R2 you should have no problems, but we are discussing and explaining the possible issues in the following articles http://www.dataease.com/test_article_view/?ArticleID=00040&field1=00040 http://www.dataease.com/test_article_view/?ArticleID=00037&field1=00037 In general we recommend Opportunistic locking in all versions of DataEase now. This included 6.53. The view on locking have changed over the years, with changing use of databases. Originally they were mostly used in accounting type systems, and the idea was that everything needed to be complete consolidated and consistent at all times. With the emergence of distributed thinking and wider use of databases in almost every application, the view became that the problems caused by this didn't outweigh the benefits of speed and flexibility. One then moved more to the view that data are dynamic anyway, and the idea of "freezing the world" to take an accurate snapshot didn't work. i.e. the "Chinese Census problem" - Should one deny people to die and be born when one did a census? If everything else works fine for you in 6.53, you can safely buy it and if it turns out that locking doesn't work for you in the full version, we will refund you the cost of upgrading it. Again sorry for not realising that you were testing the demo.

OK, let me see but as you say in the main page of the doewloads, this it´s a "FREE DEMO! Same as Full verson........." Also let me tell you, with the last version I have problems with the "fake virus detection".

Fair point Carlos. Victim of the copy and paste ghost. It is now corrected and it states that Demo is limited to 30 records and NO Network support. However, I think that it shouldn't be. On my initiative we changed from the same limited demo as 6.53 in 7.2 to Trial with timebomb. I think that a Demo/Trial shouldn't be limited at all, so I have to agree with your thinking and assumption, but the reason that it currently is you see below. We are currently working on a completely new licensing model and engine for all DataEase versions. With this engine, licensing will be more flexible and dynamic. Any customer will use the same key, but it can dynamically change from Demo to Full, and include both Full and Runtime/Exec users. DataEae 6.53 was originally launched as an "emergency" version to help DFW 5.x and 6.x users that moved to Windows 7 to discover their versions didn't work. It was never supposed to be a major version, with all the bells and whistles. This is why we retained the original licensing model, locking model etc. Never would we have thought that it would become this popular, but it has and that is why we are currently spending quite a lot of resources in bridging the gap between 6.53 and DataEase 8/DG3.