Simplicty and flexibility!


Visitors: 202,607

Radioboxes - how to filter on them and clear them

Download Sample

You can of course add a choice (default maybe) that is None or something like...

Written by DataEase 01/02/21 at 11:08:34 Dataease [{8}]FIVE

DE9 - A quick preview of the NEW interactive DQL editor.

Just a quick preview to show you all that we are not just relaxing here at DataEase

As you can see it is just a simple test done in the "horrible" Club ParaDEASE. Enjoy

Written by DataEase 18/11/20 at 21:06:06 - 4 people have commented. The newsest comment is 544 days old. DataEase 9 Developer

How to edit RDRR file to connect lost files.

All of you will at some stage get the problem when you change a form/table that it crash and the file is "lost". 

it is never lost.

The data is still there in a Temp Form XXX table. The problem is that the change crashed in the mi...

Written by DataEase 10/09/20 at 13:33:54 Dataease [{8}]FIVE

"System error: Relationship limit 255 exceeded. " - Understanding Relationships in DataEase

In regular intervals we get support request in regards to this message and what you can do to increase the limit to OPEN relationships in DataEase.

If you are "lucky" you get this problem wi...

Written by DataEase 03/09/20 at 10:53:34 Dataease [{8}]FIVE

DE85- 100% control of the USER!

Download Sample

We got a request on the form about how to use Modal and switch between f...

Written by DataEase 19/08/20 at 14:32:40 Dataease [{8}]FIVE

Beta 33% 09.11.19 - A Dataease version fully built in - Dataease

The time has come and today we let the cat out of the bag - for the first time we let anyone outside our closet partner network see and play with DE9.

We call it Beta 33% but don't make that put you off. It is a fully working replacement for DE8.5 which was the first milestone we wanted to reach before we let it out.

However it is much more than that which you will quickly find out. The reason we call in 33% is because it is at this stage only 33% of our ambition for DE9.

So within these 33% you find all the functionality from DE up to and including 8.5 final with over a 100% new functionality partly revealed today and to be revealed and evenly spaced out increments over the next 3 months.

100% DataEase

LegEasy4DOS Professional is a "pioneer" that showcase the future of DataEase.

No! The future is not retro, and the bit about it that is pioneering is not the fact that you can fun DataEase for DOS applications.

That feature is basically just how it should always have been and a catch-up with our history.

Take a closer look - The entire product is made IN DataEase following up on a "slogan" we had when we sat out to refurbish DataEase.

DataEase need to be made in DataEase!

LegEasy4DOS - How it works?

The interest in LegEasy4DOS has been "overwhelming" since we released it at the end of last week.

A lot of eagerly awaiting Professional clients jumped at it and the feedback was not late to come.

Most of you are overjoyed and excited by this opportunity to run DataEase for DOS in a modern environment, and more than happy to scrap your old XP computers and Novell servers that has kept you up at night with worry - when will it draw its last breath and what will I do then?

However not all feedback is good and some of you have been "disappointed" too.

Some of this disappointment is down to us having problem with our server park after the release due to an unexpected heavy load - don't they always say that - but some of you have been running bench mark tests and compared it to "Native" DfD on Native XP, WIndows 7 x32 etc. and the results has baffled you.

Why is it sometimes much slower and then sometimes much faster than the comparison?

In the article below we will try to explain this and how LegEasy4DOS is designed and how it works.

LegEasy4DOS Professional Release 05.08.16

The response to our Personal version of L4D has been fantastic and it has given us great motivation in the work leading up to the release of our long awaited Professional version of L4D.

We won't spend too much time extrapolating its virtues here but limit ourselves to announcing it's release and showcase its beauty ;-)

Further down the article you will find the FREE FOR ALL Trial Key you can use to get the first "spin" in this brand new interpretation of DataEase (for DOS).

New Support Manager and new Support Products introduced

For a long time we have been focusing on improving our software products, but we have now entered a new phase where we will focus more and more on the entire customer experience.

One issue that has been raised more often than others is the lack of a dedicated support service so this is one of the areas were we will now focus.

Last month we hired Fatma Adel as our new Support Manager. She has now had some time to settle in and are more than eager to start helping you resolve your issues.

LegEasy 4DOS - Update!

We are and should be very happy when an upcoming release of a DataEase product cause this much of a stir, but it is also a sobering moment.

We obviously still have some catching up to do with our new products before they reach the same popularity as the early versions of DataEase.

Luckily the "re-launch" of DataEase for DOS is part of our DataEase infrastructure strategy so you will now be able to run your legacy apps well into this century when at the same time integrate them with the latest DataEase technology.

Locking Strategies for dummies!

Ever wondered why you have so much trouble with inconsistency and being locked out of your DataEase database? If the answer is YES, read one and discover how you can easily remedy it.

Full, Basic, Opportunistic - What does this really mean? We get a lot of questions about which locking to choose in DataEase, and the answers we have give - are giving, have changed over the years. I guess that if this was a simple as it "should be", there wouldn't even be three options in DataEase, and we wouldn't leave this is in your hands.

I have spent quite a lot of times over the years debating and exploring this myself, and the problem is that it is more of a philosophical problem, than a technical one. Pictures this as going into a Chinese restaurant and ordering. You get a many with 500 items, and you are vaguely familiar with 3 of them, so what do you do. Choose what you know, or go for the set menu...

[{8}]five Release and Release program.


DataEase {[8}]five went into production today and from now on it will be all about 8.5 and beyond.

We have now concluded the longest Beta program in DataEase history - 427 days or over 1 year and 2 months.

So why so little fanfare on this watershed day?

Warning! Price increase on DataEase 8 from January 1st

We are changing how we license DataEase from Januar 1st 2016.

In short we will stop dividing licenses (and executables) in Developer (Full) and GROUP (Runtime) and introduce a simple User License and one executable that will be either a development environment or a Application Launcher based on the users privileges.

The change might seem dramatic at first, but you will get much more functionality and flexibility.

This is just an early warning to those of you that plan to buy DataEase 8 in the near future, more information on the change in product and licensing strategy will follow.

Dynamic Design - A New paradigm in DataEase development

ExecDQLClass(), CreateTable(), AddColumn()* signify a complete breach with previous DataEase thinking.

From its infancy in the early 80ies and throughout its life until DE8 there was a clear divide in DataEase between Design and Runtime. (At least in the head of the designers, but the fact that most people used it interactively and added and changed to it in real time was not taken into account)

Tables, Scripts, Forms, Reports was froozen in runtime and there was few if any way you could make your application dynamic.

How this has changed in 8....

How to create CDFs for use in DE8/DG3

This is how you create your own CDFs using Visual Studio 2013. I selected to use this version because any one can get a full version for free as long as you register with MicroSoft. You should be able to recreate this in any version of Visual Studio in almost the same way as described here. Not much has changed in creating Windows DLLs in the last 20 years. You probably can do the same using other compilers as MinWin GCC and Embarcadero, but that is outside the scope of this document.

Migrating from DFW 5.x and 6.x to DE8.5 including National Versions

If you want to encompass DataEase problems in one word it must be Migration. It is fascinating that a company that has had so little success with this concept, has sworn to it for such a long time.

It is a badly hidden secret that DataEase lost most of it users in the flawed and bodged migration of DFD application to early DFW, what is maybe not so well know is all the other "unsuccessful" migration events.

In this article we will explain what/why and how it went wrong and what you can do to work around it.

We reached our 1.000.000 visitor today 23rd of February 2015

At the beginning of the year we had estimated that we would get our 1.000.000 visitor at the 6th June this year, but with the Beta of 8.5 and the great feedback we have seen both visits on our website and sales sky-rocket and we reached the 1.000.000 threshold more than a Quarter ahead of schedule!

We just have to thank you all for your patience with us, and for your contributions and support throughout the last couple of years since we took charge.

We both hope and feel that our efforts and enthusiasm for DataEase has been well received and are reciprocated by you all!

A wholehearted thank you to your all from "The DataEase Team".

NEW! Functions in DataEase 8.0 to 8.5 (Page 1)

Some of you might be aware of it but it seems a lot isn't so it might be time to advertise a little the vast number of new functions and functionalities that has been added to DataEase 8.0 through 8.5.

For a long time the only way new functions found their way to DataEase was through active and ingenious users which developed CDF's. As much as the CDF's alleviated the obvious short-comings in DataEase 5.x to 7.2 it was cumbersome, undocumented and "secretive" i.e. not everyone was in the know.

With 8.x we decided that the focus needed to be on moving DataEase forward, rather than the constant dance around the "bug fixing" fire.

Have a look and a try for yourself.

Due to the number of new functions we had to publish the short description in two articles, of which this is the last.

Also have a look on the blog synopsis found in the list to the right.

Start your own thread!

04/10/22 08:06:28

Re:DE6.53 - Error 1 opening application , operation fail

Seems that a file must have been locked by one of the logged on users


Product: DataEase 6.x

Written by: Sam Bird

04/10/22 07:11:47

DE6.53 - Error 1 opening application , operation fail

How to recover from this error message on DE6.53?

Error 1 opening application , operation fail


Product: DataEase 6.x

Written by: Sam Bird

26/09/22 23:33:03

Re:Re:Re:Re:Re:Re:Re:Re:Re:Re:Re:Re:Re:DE8 Lookup listbox field - please specify the Bound Column to create Lookup Field?

Did you run the re-compile option after migration?


Product: Dataease [{8}]FIVE

Written by: Sam Bird

26/09/22 21:37:44

Re:Re:Re:Re:Re:Re:Re:Re:Re:Re:Re:Re:DE8 Lookup listbox field - please specify the Bound Column to create Lookup Field?

Not sure what you have done, but we made an app in 6.53 with a lookup field, migrated it to 8.5 and it worked perfectly without any intervention on our part.


Product: Dataease [{8}]FIVE

Written by: DataEase

26/09/22 11:18:53

Status bar record count vs percentage

In DE6 the current record number and total table record count is shown in the status bar on forms.

in DE8 it gives a percentage instead of current record number.
Is there a setting to change the default to record number?



Written by: Sam Bird

26/09/22 09:40:20

Re:Re:Re:Re:Re:Re:Re:Re:Re:Re:Re:DE8 Lookup listbox field - please specify the Bound Column to create Lookup Field?

Thank you, it works now.

This was not required in DE6 which implies that all old forms with lookups will have to be updated manually.

Is there some other new option now other than 'bound' which requires 'bound' to be selected for lookup?


Product: Dataease [{8}]FIVE

Written by: Sam Bird

25/09/22 18:54:14

Re:Re:Re:Re:Re:Re:Re:Re:Re:Re:DE8 Lookup listbox field - please specify the Bound Column to create Lookup Field?


You need to click on Instrument_nm and then click on Bound.

Kind regards



Product: Dataease [{8}]FIVE

Written by: Josef Vella

24/09/22 15:19:52

Re:Re:Re:Re:Re:Re:Re:Re:Re:DE8 Lookup listbox field - please specify the Bound Column to create Lookup Field?

Any idea how to resolve this?


Product: Dataease [{8}]FIVE

Written by: Sam Bird

23/09/22 12:59:32

Re:Re:Re:Re:Re:Re:Re:Re:DE8 Lookup listbox field - please specify the Bound Column to create Lookup Field?

Test app attached.
user name = DEV 
pwd = de85
Form: Usage
           Field Instrument must be set with lookup using relationship rI_U to list selection values from Instruments table.


Product: Dataease [{8}]FIVE

Written by: Sam Bird

23/09/22 12:36:35

Re:Re:Re:Re:Re:Re:Re:DE8 Lookup listbox field - please specify the Bound Column to create Lookup Field?

Multibox leave a lot to be desired but in general it has worked so I'm not sure what goes wrong here. Can you send an example of what is not working?


Product: Dataease [{8}]FIVE

Written by: DataEase

23/09/22 12:06:05

Re:Re:Re:Re:Re:Re:DE8 Lookup listbox field - please specify the Bound Column to create Lookup Field?

Ok, i can understand that there are challenges with migration and issues must be resolved.

The real problem is this does not even work on a new non-migrated app.


Product: Dataease [{8}]FIVE

Written by: Sam Bird

23/09/22 10:51:23

Re:Re:Re:Re:Re:DE8 Lookup listbox field - please specify the Bound Column to create Lookup Field?

That figures.

Migration has always been the "downfall" of DataEase. Sadly the problem was done in 7.x and since then its all about trying to make square pegs fit in round holes.

The lookup fields in 6.x was fit for purpose so the idea to then change them into this "multibox" idea was disastrous. Suddely a simple lookup field should also be CTRL-F10 and a jack of all trades, and the way its defined is changed radically.

8.5 is out of development and migration from pre 7.x is no longer a priority for DataEase so obviously this is not ideal for you but there is limits to how much resources we can put into migrations as whatever we do at this stage, a significant effort from the user will be necessary to get a good application.


Product: Dataease [{8}]FIVE

Written by: DataEase

23/09/22 09:49:31

Re:Re:Re:Re:DE8 Lookup listbox field - please specify the Bound Column to create Lookup Field?

Unselect / reselect as many times as you want - still the same error.

This is on a new application although the problem was first identified on the app being migrated.

This is a massive problem as the app being migrated contains many lookup fields.

Some fields work ok after migration but others do not work.

What was also noticed is if a form contains a working lookup field and an edit is done on the defining form then the lookup field definition does not show the lookup and the form is saved after edit then the lookup no longer works. The lookup can also not be fixed as this 'bound' error occurs.


Product: Dataease [{8}]FIVE

Written by: Sam Bird

23/09/22 09:28:09

Re:Virtual field allow entry new feature?

"New" I guess is maybe not the word as DE8 is not exactly new anymore but it is intended behavior yes and not a bug.

Just because a field is virtual doesn't mean it can't be used as an input field or you shouldn't be able to copy from it. 

Stagnant thinking was very long the only thinking in DataEase and by easing up and not taking things so literally things flow much better.

For a long time people here believed DQL was "Report" i.e. something you printed out, while in reality it has very little to do with reporting and everything to do about processing hence ExecDQL which is headless DQL. 

While you run ExecDQL you don't have a data-entry form (which in a way you never should have had) but simply either transfer arguments via the 4 fixed ones in the function or via SetVar()/GetVar() or pick them out from the document with GetValue() and Set them directly back in the Document with SetValue().

I once had a discussion with our previous head of development about the limitations on Memo. That we couldn't use Memo outside of 128 characters in processing and that we couldn't manipulate or populate a Memo programatically.

The response was - Its called MEMO for a reason. Its for memo's i.e. things typed by the user. I thought he was joking but he was dead serious. It kind of explainde a lot. After that we did the Memo class of manipulation functions and in DE9 we have completely removed any limitations in string handling (which he also said was impossible to change) so all string functions now handle and return up to 4gb rather than the paltry 255 (rather 253 to be safe) in all versions from 1.0 to 8.5.

We will keep removing this unnatural boundaries and limitations as we move forward.

in 9.5 we are going to remove Data-Entry forms and simply just use the form you fire the DQL from as data-entry form directly for instance. How it should always have been to be honest.


Product: Dataease [{8}]FIVE

Written by: DataEase

23/09/22 09:26:50

Re:Re:Re:DE8 Lookup listbox field - please specify the Bound Column to create Lookup Field?

Try to unselect it and select it again. 

Multibox was one of the "innovations" in DataEase 7 and maybe not the most thought through idea. It has been much improved in DE9/LE9. 


Product: Dataease [{8}]FIVE

Written by: DataEase

23/09/22 08:13:40

Virtual field allow entry new feature?

In DE6 setting a field as virtual would also set it as 'Prevent Entry' as this was typically used for dynamic derivations.

In DE8.5 setting a field as virtual allows it to be set to allow entry or prevent entry.

Is this a new feature?


Product: Dataease [{8}]FIVE

Written by: Sam Bird

23/09/22 08:12:12

Re:Re:DE8 Lookup listbox field - please specify the Bound Column to create Lookup Field?

Take note of the screenshot - the bound column is selected.



Written by: Sam Bird

23/09/22 08:05:37

Re:Re:Remove Designer view application function buttons

The Design toolbar takes up screen space while most functions are not required very often during the design process.

What is the entry required in Dataease.ini to remove it?

the following entry does not work.




Product: Dataease [{8}]FIVE

Written by: Sam Bird

22/09/22 20:31:51

Re:Make it Stop

The error message is wrong. it say DBA but the problem is a missing .TDF file.
It is something in your document that reference a column in a table that no longer exist.


Product: DataEase 8.5 Runtime

Written by: DataEase

22/09/22 20:30:17

Re:DE8 Lookup listbox field - please specify the Bound Column to create Lookup Field?

The bound column is the column that will be the return value for the Multibox. You have to select one.



Written by: DataEase

DataEase Mainpage