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.
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.
13/09/26 23:32:44 
Re:Disappointed In Dataease
Hi again Steve.
I used to be in your position - throwing stones at Sapphire and being frustrated with every new version not doing what I wanted.
Its easy to be frustrated at both ends so I will went "our" frustration too...(Not the way you fear ;-))
LE9 (DE9) while still looking deceptively like DFW can in reality to almost anything and have non of the limittation of previous DataEase versions.
However it is not a "magical" tool that just do it for you, so one have to invest in figuring it out and using the new stuff etc.
That has been very much our frustration that most users focus on everything that is "not as before" whille not spedning much time on anything new or wanting to learn new way to do things.
Obviously that is our "problem" as its our job to educate and motivate so I'm not telling anyone off but rather quite openly say it how it is.
You have a DE9/LE9 license so obvioulsy have full access to all the new stuff etc. but you are still disappointed.
Can you eleborate?
Forget about the company etc and lets focus on the product. What is it specifically you are disappointed with in LE9? What is it you would have like it to do for you?
And lets dream a little!
What had you pictured that DataEase would have looked like in 2026 and again what would you like it to do and in what way?
It's not a trick question, we are genuinely interested and wouldn't it be fun if it already did what you want it to do?
We invite anyone to write the same and we will respond with an open mind and if LE9/DE9 already do it we will provide a sample for you on how you can do the same.
Most people that use LE9 absolutely love it - and that is not he normal spinn, its the truth - but its easy to fall into the trap and think its just another repainted DFW version which couldn't be further from the truth.
Lets start a dialogue on here on what you want and then we can provide the solution.
If you come up with good ideas we haven't though about then we will consider making that part of the product too.
...
Product: Dataease 9 Developer
Written by: DataEase
13/09/26 22:55:39
Re:Disappointed In Dataease
Hi Steve.
As we are all previous users that got togehter to take over DataEase from Sapphire we know very much the feeling you have.
When you mention a "regular poster that get frustrated" I thnk you must mean Ihor and I must disappoint you in that regards. We are great friends with him but we do admit that some times the tone can get a little frustrated both ways ;-)
DataEase is now over 45 years old and we have customers that use versions from 4.53 to LE9 with everythng in between.
We have had solutions for web/apps/integration REST etc for over 10 years but the problem is what to productise. When the new team took over the first priority was to support exsisting customers and very much of the development and resources has gone towards helping them out hence the focus on L4D and the first increment of DE9 being called LE9 (LegEasy9).
The sad truth is that since DataEase for WIndows was launched with the challenges that was for both customers and DataEase the focus has been on supporting exsisting users rather than build a product for new users.
DataEase for WIndows is a massive and complex product that is very hard to tailor both for existing legacy usres while a the same time be an attractive solution for new users.
Another problem is that based on previous experiences with migrating from DFD to DFW and from 6 to 7 etc. a lot of users are "afraid" of upgrading and the "original" generation of DataEase developers/users mostly want things to work as before rather than spend time on moving fowards etc.
LE9 (DE9) is the easiest and most advanced version of DataEase that has more new and improved features than all previous DataEase versions put together but we haven't "blown the trumpet" as we still don't think that its a version that will recruite new users.
DataEase work with large customers in the UK and around the world that has DataEase as a business critical application. You migh tnot believe it but there are still large corporations out there with thousands of DFD users as well as DFW applicaitons. Most of them have tried to get rid of DataEase since the 1990s but they never found anything that could do the job the same way so they have stayed.
The main driver for them movign forward with DataEase is a change in the generation that support DataEase internally with them. They get young people that undestand that this app - though old and outdated - do something that most modern tools they have seen can't so rather than replace DataEase they want to modernise and use it more.
The main hurdle is that the systems are in daily use and the "migration/redevelopment" is a death trap.
Nobody like migration old code so we decided that we would rather allow them to keep running their old apps (LE9) and then we could support them with building around the app on top of the dame data.
So LE9 is in many ways a "trojan horse" as it open up the database to modern tools. We now run hybrid apps including DFD/LE9/Web and apps with itegration to online services and other databases.
We are aware that there has been many "false starts" with DataEase and that is why we have not updated the website and treat it more like a communication hub with existing users and a resource to buy DataEase for the people in the know and for users to download upgrades etc.
The simple truth is that its very costly both in money and resources to support any product and hence we have to take the time needed to get the right prouduct out there that we can support.
So the future of DataEase is very much divided with LE9 being the product to support existing users - which has been and always will be a priority for us - and a new product for new users that hopefully will succeeed in going back to the roots of simplicity and rapid development.
We obviously know more about what is coming but as you have pointed out - there has been to many promises and previews that didn't materialise so we now think its better to wait till we are ready rather than stir the pot.
At the moment we concentrate on being here for the ones that already use DataEase and make sure they can keep using it as they have and want to and also help them moving forward but our long term goal is still to claw back the position DataEase once had but only time will tell if we get there.
...
Product: Dataease 9 Developer
Written by: DataEase
12/09/26 20:43:41
Disappointed In Dataease
I am sorry to say I have actually lost faith in Dataease, I understand that building software is a resourceful and time consuming task but the time its taken to get to this stage from a load of early promises is not the best advert for a product. I have given up waiting and I know many others who will have done the same over the same period, in particular a regular poster on the forum who understandably gets angry and frustrated over the delays, after delays. This is usually followed up by Dataease replying in a similar manner which probably does not help matters. The original intentions were probably ambitious but the outcome has not been. I wish you all the best for the future and hope you can achieve what you set out to do.
...
Product: Dataease 9 Developer
Written by: Steve_C
04/09/26 11:13:30 
Re:Re:I'm an old, old, old DE user (4.53? I think) ... I need some menu screen shots please!
PEACE. I love to visit NY subway excursion still.
wish UGOS team all the best
...
Product: DataEase for Windows 5.x and before...
Written by: Ihor Zakharchenko
01/09/26 19:32:07
Re:I'm an old, old, old DE user (4.53? I think) ... I need some menu screen shots please!
I know this is a very old thread. But I'm just coming here today because I am remembering fondly my days of Data Ease. It was my first programming love. I fought against windows back in the day because at the time DE wasn't built for windows. I tried to get the U of M to switch to DE because it's what I knew! LOL! Anyway, I loved seeing Suzanne's post here. PEACE.
...
Product: DataEase for Windows 5.x and before...
Written by: Gina Maylone
26/08/26 20:55:20
Re:Re:Lengthy Export/Delete Time
besides indexing reindexing the next tip is obvious even more … but shoking .. ready ? Lets go ;)
I am very sorry … excuse my Ladies & Gentlemen ..
The only way… is binary coding not assembler for sure no no nio
Direct access to physical devices as memory , disks and etc. via machine coding
Nothing with high level but generally very dlowcnon effective code
Don't forget in that world of 0 and 1 … yup … 1+1=0
This id from my working practice since 1978 … to be exact with Soviet clone op Hewlett-Packard mini terminal of data connection for power energetics … the only way to get time shortage . So even dBase db in the case was more speedy than … keep silence nevertheless
...
Product: LegEasy 9 Developer
Written by: Ihor Zakharchenko
25/08/26 09:57:50
Re:Lengthy Export/Delete Time
Download Sample (big)
there is several ways to export data from 8.5 so to start solving this we would need to know what method you use?
The "quirky" workaround in DQL with
export to "c:\blat\export.txt" .
RecordID~TransactionDescription ~Text ~Value ~Currency ~CurrencyValue ~Rate
.items ole
@f[1,1]~@f[1,2]~@f[2,1]~@f[2,2]~@f[2,3]~@f[2,4]~@f[2,5]
.end
Is the absolutely slowest and also seem to be very variable from slow to extremely slow to never..
Over the years we have looked at several workarounds and even back in early 8 we changed the export function so it would take a definition etc. so one could make a "hack" in DQL to use a export definition instead which is much faster than the "export to" stuff which was a bad implmentation of a bad idea.
DataEase 8.5 is a long time ago now and a lot of stuff has moved forward since then, also in the areas of export etc.
In LE9/DE9 you can basically either use ExecDQL or the built in export feature in DQL which is blitzingly fast. (see above).
You can also open any DQL for Export etc. via DocumentRun() where you can tell it what you want it to do and where you want to send the export.
https://www.dataease.com/dg3_HelpView/?PageID=1382...
There has been a "habit" of using temporary tables in DataEase/Ffenics to move data to before exporting/manipulating/reporting etc.
Most likely this was done as things didn't work as they should in DQL/Reporting but it was never very good advice as one of the slowest things you do in DataEase is to do a conditional delete i.e. "delete records in temptable with owner = current username ."
But if one use temporary tables then one should flush it rather than delete row by row i.e. delete records in tablename . (this drop the table). rather than For Tablename with etc ... delete records or delete records in mytable with owner etc. as above.
And when you use temporary tables DON'T USE INDEXES! it is the index updating that slow down the process most as this is done for each row.
This is good advice in general - to be very careful with index us!!! Most people wrongly assume that indexes speed things up but that is only true when used correctly and wisely.
Maintaining the indexes is what slow down insert/modify and delete and it only help with searching up in very big tables when you search in the correct field in the correct way... So mostly avoid if you don't understand them
Try to search for anyting in the Companies table in our Toolbar freetext search (remember this is close to 2 million records). You will see that it takes time but not anything like you think and then it has searched through ALL the records for ALL occurences.
In the sample, you can see the code and speed for exporting data in different ways and you will see how fast the DE9/LE9 way is compared to the traditonal and you will see how flexible ExecDQL is in creating the output format you want.
...
Product: LegEasy 9 Developer
Written by: DataEase
25/08/26 08:57:45
Re:Lengthy Export/Delete Time
hi! It is obvious to delete and export just in time … before exceeding that critical amount of records … other tricks are risky in de … indexing ….. reindexing etc.
...
Product: DataEase 8.5 Runtime
Written by: Ihor Zakharchenko
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. Ive 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 doesnt work nevertheless .?as in DFD I used numeric string sequence from 1 in derivation … Ive 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
Register
Sign In
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...
