Simplicty and flexibility!

-

Visitors: 17,799,349

LE9-How to call ExecDQL directly from code

ExecDQL started small and is now all-encompassing. What started as a way to execute a DQL for processing with no output now powers websites and has taken on a life on its own w...

Written by DataEase 08/11/24 at 15:16:23 - 1 people have commented. The newsest comment is 653 days old. LegEasy 9 Developer

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 1,962 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

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.

Finally...

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.

NEW! ?Functions in DataEase 8.0 to 8.5 (Page 2)

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 first.

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

Start your own thread!

23/08/26 03:19:42

Lengthy Export/Delete Time

Hi All, Any way to make exporting data any faster in DataEase 8.5? If I'm exporting several hundred thousand records it can take hours. Anything under 100k records seems to export much quicker. It can also take a long time to delete a large number of records. Your advice would be greatly appreciated.

...

Product: DataEase 8.5 Runtime

Written by: Bolt-on-Trailers

21/08/26 15:41:48

Re:Re:Re:Re:Re:Re:Re:Re:Re:Re:Re:Re:Re:New release of LE9 17/0726

thx. I support modern DataEase no DFD but the case with table firm shifting , F2 F8 or simply PgDn PgUp on the table view mode makes real sequence in DFdD very easy and speedy nevertheless. I’ve solved my task with DFD easily … my aim is to work with modern DE10 or how you all brand it in the nearest … hope.. future . Glory to DataEase team … but I am not confident to be alive after this hungry and. Old winter due to the missile attacks … sorry

...

Product: LegEasy 9 Developer

Written by: Ihor Zakharchenko

21/08/26 15:30:35

Re:Re:Re:Re:Re:Re:Re:Re:Re:Re:Re:Re:New release of LE9 17/0726

Its the test that is flawed not the functionality.

To make sure you don't get numbers out of sequene the number is allocated ON SAVE the first time you save,not when you tab over the field.

You simply go down the screen without saving will render all with the same sequence number in table view.



the XX- is the giveaway of a new record not yet saved.

Second flaw is in table view it won't save records that hasn't been manually entered into so not to save rows that has been mistakenly created like the 5 and 6 above.

When I now hit F8.

Row 4 is still row 4 and rown 7 is now row 5.

There has been many fixes to this functionality over the years and CDF's like Uneek etc. was created by people that liked th pick a number functionality before saving etc

The problem with publishing a product for close on 50 years is that a lot of people think that how it used to be was better than how it is hence the sample that "confused" you that show how you can get other functionality than the standard.

This is the standard functionality and it works - I will use a hated sentence - as designed... ;-)

...

Product: LegEasy 9 Developer

Written by: DataEase

21/08/26 12:14:55

Re:Re:Re:Re:Re:Re:Re:Re:Re:Re:Re:Re:Re:New release of LE9 17/0726

...

Product: LegEasy 9 Developer

Written by: Ihor Zakharchenko

21/08/26 10:37:56

Re:Re:Re:Re:Re:Re:Re:Re:Re:Re:Re:Re:New release of LE9 17/0726

...

Product: LegEasy 9 Developer

Written by: Ihor Zakharchenko

21/08/26 10:19:48

Re:Re:Re:Re:Re:Re:Re:Re:Re:Re:Re:New release of LE9 17/0726

...

Product: LegEasy 9 Developer

Written by: Ihor Zakharchenko

20/08/26 22:22:22

Re:Re:Re:Re:Re:Re:Re:Re:Re:Re:New release of LE9 17/0726

Firstly, we are not trying to go backwards. There is a lot of water under a lot of bridges since DFD.

Our goals has never been to re-create DFD and DFD is in no way the gold standard for how things should be.

DFD was great for its time but its a very outdated way of thinking, what we can learn from DFD is simplicity and logical evolution but to try to copy 1980's ideas in the 2020's will not be a success.

However it is exactly the same.

You can even make a numeric string field and typ squence from 1.

There was never an increment you could set, it was always increase by 1.

For most users its easier to select a sequence field than having to type the formula but you can do both. if you use sequence from in the derivation the field gets classed as a sequence field but in reality there is no such thing, it is just a UI feature.



If you do the same in a text field you will get.

and if you use just sequence from "AAAA" 


...

Product: LegEasy 9 Developer

Written by: DataEase

20/08/26 18:16:52

Re:Re:Re:Re:Re:Re:Re:Re:Re:New release of LE9 17/0726

it doesn’t work nevertheless .?as in DFD I used numeric string sequence from 1 in derivation … I’ve got sequence ID type automatically and no incrementation in fact . I am sorry but s hm ow me the ease and right way as it was in DFD in my 1989-1996 practice .  We organized our Ltd May 17th , 2006 especially inspired by and for de 7.*  but it is 2026 and …still. Maybe DatAI or how it is called that the newest lrkductvIvam hoping to see before missile consisting of western electronic despite of declared sanctions will kill all around me and me forever.

...

Product: LegEasy 9 Developer

Written by: Ihor Zakharchenko

20/08/26 12:32:12

Re:Re:Re:Re:Re:Re:Re:Re:New release of LE9 17/0726

got it at last! The version is ok too. As to the year  in copyright it is still 2022 … may be due ti the war too …  it the war lasts since 1054 … here 

...

Product: LegEasy 9 Developer

Written by: Ihor Zakharchenko

20/08/26 12:25:34

Re:Re:Re:Re:Re:Re:Re:New release of LE9 17/0726

ok. now there are problems with downloading on our side may be due to this morning rocket attack..but we shall overcome nevertheless. thx .Glory to DaraEase team!

...

Product: LegEasy 9 Developer

Written by: Ihor Zakharchenko

20/08/26 09:20:39

Re:Re:Re:Re:Re:Re:New release of LE9 17/0726

Sorry, this has now been corrected.

...

Product: LegEasy 9 Developer

Written by: DataEase

19/08/26 08:50:23

Re:Re:Re:Re:Re:New release of LE9 17/0726

...

Product: LegEasy 9 Developer

Written by: Ihor Zakharchenko

19/08/26 08:36:02

Re:Re:Re:Re:New release of LE9 17/0726

Mate! Undoubtedly! The misunderstanding caused simply by the Sequence app and 7342 instead of 7441 release… Glory to DataEase team nevertheless ! Will try again being more attentive …thx 

...

Product: LegEasy 9 Developer

Written by: Ihor Zakharchenko

17/08/26 12:09:45

Re:Re:Re:New release of LE9 17/0726

It stil does that and always have.

...

Product: LegEasy 9 Developer

Written by: DataEase

15/08/26 12:46:49

Re:Re:New release of LE9 17/0726

... for I need old good numerical string with sequence from 1 derivation as in old good dfd ... 

...

Product:

Written by: Ihor Zakharchenko

06/08/26 18:39:24

Re:New release of LE9 17/0726

downlpaded installed cheked ... 7342 still

...

Product:

Written by: Ihor Zakharchenko

06/08/26 09:49:33

New release of LE9 17/0726

Hi, all! Just got 7441 … but the downloaded file is 7342.exe … suppose it is 7441 nevertheless … the question in advance then … my license key as always . Thx a lot ! Glory to DataEase Team ! 

...

Product:

Written by: Ihor Zakharchenko

30/07/26 17:52:36

Re:One thing I don't understand, why you even need the data-entry values?

old good de 4.53 db with sequence from 1 got strange behaviour in table view and the keyboard tricks of fujitsu siemens laptop / thx for emergency aid nevertheless. Glory to DataEase team!

...

Product: LegEasy 9 Developer

Written by: Ihor Zakharchenko

29/07/26 09:33:02

One thing I don't understand, why you even need the data-entry values?

define "newnumber" number .

for SequenceStore with Name = data-entry field1 and data-entry field2 not = "yes" ;

newNumber := CurrentNumber + Increment .

modify records

CurrentNumber := newNumber .

list records

newNumber .

meaning this >>> with Name = data-entry field1 and data-entry field2 not = "yes" ;

...

Product: LegEasy 9 Developer

Written by:

28/07/26 14:46:51

Re:What is the best way of making a sequence?

Download Sample




Obviously the standard Sequence field but if it was that simple I guess you wouldn't have asked.


There has been a lot of "fixes" to the Sequence field (sequnce from 00001) over the years and confidence in the functionality have taken a beating.

We use it all the time but mostly just to get a "unique" ID for reference in lookups etc, rather than a completely guaranteed squence.

In the attached sample we "discuss" some ideas and ways to do it and we also showcase how you can use ExecDQL both as a function, inline and in a combination.

The sample is just for ideas and inspiration and you have to finish off how you want to use it yourself based on what is important.

We have a simple example that simply pick the Sequence from a table on load and update the value back immediately. This will make holes in the sequence if you don't store but you will never get two records with the same sequence.

We have one sample that use highest of in an execdql and update on save and another that use the sequencestore table as the first but run a ExecDQL "function" and update on Save again after having picked a "temporary" sequence on load.

Have a go and use it as you please.

...

Product: LegEasy 9 Developer

Written by: DataEase

DataEase Mainpage