I return to a topic already covered both on the Forum and on your Blog.

http://www.dataease.com/DG3_ForumList/?ParentID=0000002812&field1=0000002812

http://www.dataease.com/DG3_BlogList/?ParentID=0000000494&field1=0000000494

Sometimes a wrong items is generated in the catalog file RDRRxAAA.DBM which causes the following error when the database is opened:

It has been repeatedly indicated how to correct the error but nothing on how to avoid generating it.

This error recurs periodically in the database for no apparent reason for the $DeStat_DQLInfo$ item which is a system table repeated many times in this file.

Obviously, by correcting the last item from 0C to 0F, everything is resolved.

So the problem lies in the product, how can I prevent this from happening all the time?

Thanks.

[DataEase 8.5]

The problem is related to an automated update routine that look after the Status tables in DFW. 

When it identify that the current version is "outdated" it will replace it and if this replacing goes wrong you get your problem.

As it is highly annoying and these tables are not critical we have in future versions removed this old fashioned updating approach.

However they are still there in 8.5 so what you can do to stop this from happing is to syncronize the files "manually".

I.e. set the 0e to 0f on all occurences of DQL info in the rdrrr and delete all files that correspond to the entries in the app.
Then start over and DE85 will create the latest version and after that it will be in sync.

All occurrences of DQL information in rdrr report 0f except the last one which reports 0C.

I correct the last occurrence in 0f but after a while a new version is generated in the catalog with 0c and the problem recurs.

How can I permanently resolve?

This problem does not allow me to execute dataease procedures via automatic scheduling. For me it's very important.

It is not even possible for me and my Company to upgrade from 8.5 to a later version (e.g. 9.1) but only an upgrade to the actual version. (8.5)

In addition I deleted all the DBM files of the older version of DQLInfo system table but nothing changed.

Which version of 8.5 do you run.
The latest one on here has a fix for this, but it is not a 100% fix sadly.

The problem is an old mechanism in DataEase that update system files. DQL status table was updated towards the end of 8.5 development and the problem is linked to this update. It was early identified that the problem originally occured when a customer ran both a version of 8.5 before the fix and after at the same application as they would den fight about "updating" the same table.

At the moment there is no newer version than 8.5 but why can't you upgrade to a higher version than 8.5 when 9.0 is released?

I run the following the same version 8.5.1.2674 for developer and for Degroup (Player) and unfortunately I cannot upgrade to a newer version like 9.0 and over. 

I cannot upgrade to newer version because I cannot use the actual licenses valid only for 8 versions. Thanks

I think there is some mis-communication here.

We are a software company that invest a lot in development. To use our software customers need to pay to get upgrades and services. If customers don't want to pay for upgrades there is no business and no rational to develop or fix problems. 

We are a business and not a ideal organization after all.

I beg your pardon. I obviously agree with you. We area a very old DataEase customer and we'll evaluate if there's a possibility in future to upgrade the software to a new version. In the meantime do you think installing developer version 8.5.4.2674 or 8.5.5.2674 and stay on version 8.5.1.2674 for degroup (player) (this is the last version for degroup) can almost partially resolve this problem?