Simplicty and flexibility!

-

Visitors: 13,600,900

How to print a barcode via HTML

Download

In Principle you can use the same font in HTML.


Just need to set it on the tag.

<style&...

Written by DataEase 06/04/20 at 15:17:00 Dataease [{8}]FIVE

L4D - Creating New Application in L4D and why all apps are located in B:\


You can create a new application in any location on your computer.

SImply add a name for your new application, browse to the location you want to use, and hit SAVE and the Session will be...

Written by DataEase 02/04/20 at 15:20:10 LegEasy DOS

L4D - How to print with color in LegEasy4DOS


We got a request today from a customer that was testing LegEasy4DOS. 

As he was very enthusiastic about what he could accomplish we decided to set aside some to help him...

Written by DataEase 25/01/20 at 18:21:12 LegEasy DOS

DE9 - How to use DE8 Custom Menus etc.

First thing first, you can keep your DE8 filemenus, toolbar and tab bar in DE9 (even catalog) if you want to.

You can do this either programatically via SetCurrent() ex. SetCurrent("File...

Written by DataEase 18/01/20 at 12:42:51 DataEase 9 Developer

DE9 - New version and new Sample 9.0.0.4391

Download Sample

In build#4391 we consider TabControl more or less finished and we have also implemented an Action to run Exe...

Written by DataEase 06/12/19 at 14:36:26 - 2 people have commented. The newsest comment is 132 days old. DataEase 9 Developer

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.

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.

Start your own thread!

31/05/20 04:28:30

Re:Re:Re:Re:Re:nothing new still

why DQL ? for it is real AI made in 1980s by Arun Gupta. DQL makes data  ease obvious and we got DataEase as a result. If we don't see DQL in the product that means we have no DataEase. The product may be web windows English RDBMS but not DataEase in its sense.

...

Product: DataEase 9 Developer

Written by: Ihor Zakharchenko

29/05/20 14:27:41

Re:Re:Re:Re:nothing new still

don't worry about DFD... the only thing there is DQL for the only reason ... from the point of view of those who are making non invasive human -to-digital devices interface ... the future is without comps and Internet ..only humans united in one Brain via real thing=telepathy ..stop developing homunkulus ..all was designed inside biorobots named humans ...everything ... and DQL shows that.

Good luck, mates!

I am algebraist and that is all to say.

...

Product: DataEase 9 Developer

Written by: Ihor Zakharchenko

29/05/20 13:07:30

Re:Re:Re:nothing new still

The death of Windows like the death of DataEase has been predicted constantly since the 90s and still - here we both are.

Microsoft have tried to capture the "device" market almost as many times and every time fallen flat on their face. 

One thing we have learnt in this company is that "killing" off software is almost impossible and very ill adviced. The biggest mistake done here was not to include DFD applications "as is" in our strategy when DFW was released. The idea that people would migrate/re-develop apps in this "fantastic" new environment was completely flawed and for the same reason MS will keep maintaining and develop Windows along the same lines for decades to come.

They might want to move, they might try to move but if people move it is away from them to another OS rather than on to their "new" one.

...

Product: DataEase 9 Developer

Written by: DataEase

29/05/20 11:32:41

Re:Re:nothing new still

Hi, Ulrick. Thank You very much for Your reply. Please take into account that Microsoft will end up with Windows and move to X=Unix originated platforms (Windows 11 or Windows X nicknamed). That is why the question about macOS X was not a joke ...

...

Product: DataEase 9 Developer

Written by: Ihor Zakharchenko

29/05/20 11:08:49

Re:nothing new still

Hi again Ihor.

In light of the current situation we have decided to do some big re-writes of our DE9 code like switching from IE to Chromium for our internal web engine etc. This involves ripping central pieces out of the code and hence it will render the product in limbo until it has been properly implemented and tested.

DE9 will be our development hub for all products for quite some time and hence we want it to be as strong as possible. 

We have also switched quite a bit of our resources to our PURE Web offering (GoAllTheWeb) which will allow full Web development online. 

Beta is a way for us to share with you some of the ideas and functions we are working on but it is not a release product with regular updates and bug fixes. 

The latest build of DE9 Beta 33% is 4450 and the current one in development is 4712. That is almost 300 build numbers up which is over a 100 more than difference between 7.2 and 8.0 if you measure it in historic number and that took well over a year in Development.

At the moment we are not in release mode of any code but that can change quickly but as things stand now our first new beta will be "DataEase GoAllTheWeb" and then full DE9 Beta (100%).




...

Product: DataEase 9 Developer

Written by: DataEase

29/05/20 08:06:25

nothing new still

...

Product: DataEase 9 Developer

Written by: Ihor Zakharchenko

26/05/20 13:20:11

Re:Re:Re:Re:Re:1c 8.3 vs DE9

Hi, Ulrick and the Team.

DataEase is the best and that is obvious fact.

English is excellent.

as the Windows 10 Insider tester I am for Windows .

what about a little percentage to increase 33% DE9 Beta testing ? 

;) thx for understanding of humour even in the times of ... You do know what I do mean.

On the picture: Norbert Wiener (to the right) AND MY TEACHER (in the center). Kyiv, June, 22nd, 1960. 

...

Product: DataEase 9 Developer

Written by: Ihor Zakharchenko

26/05/20 12:13:29

Re:Re:Re:Re:1c 8.3 vs DE9

Hi again Ihor.

MacOS is not on our list of priorities so anyone that wait for DE9 or any other DataEase version to run natively on MacOS will wait a long time.

From this end DataEase is a business and we need to focus our resources where we make the most impact. 

Today so far we have had requests for a Farsi, French and Chinese version of DataEase and it is only 11 am.

We obviously want as many people as possible to enjoy DataEase but we need to concentrate our resources and at the moment that means:

English only.
Windows
Web

Then the next step is:


Language versions developed in correlation with strong local distributors.
Android/iOS

We know that this might be disappointing for many of our supporters but we simply can't please everyone.

...

Product: DataEase 9 Developer

Written by: DataEase

25/05/20 18:37:15

Re:Re:Re:Re:1c 8.3 vs DE9

I did not ask about DQL on DE9 for Windows or Mac OS ..for it is impossible to develop that now. but ..if on Mac DE9 will be good even without DQL ... 

...

Product: DataEase 9 Developer

Written by: Ihor Zakharchenko

25/05/20 18:32:00

Re:Re:Re:1c 8.3 vs DE9

on macOS ? thx. How to download DE9 Beta on MacBook Pro then ?

...

Product: DataEase 9 Developer

Written by: Ihor Zakharchenko

25/05/20 17:51:55

Re:Re:1c 8.3 vs DE9

Hi Ihor.

We have given you quite a lot of leeway on this forum but there need to be a limit. We develop and support DATAEASE and no other product is relevant as long as it is not complimentary to DataEase users.

We never intend to be or compete with products like 1C. There is plenty of products like 1C out there and anyone that want to use them are more then welcome to use them.

There might be many products better suited for some users or some problems but that is not something our website or our forum is designed to take care of.

Here we help people that has a challenge in using DataEase!

...

Product: DataEase 9 Developer

Written by: DataEase

25/05/20 16:57:13

Re:1c 8.3 vs DE9

https://1c-dn.com/download-trial/

...

Product: DataEase 9 Developer

Written by: Ihor Zakharchenko

25/05/20 13:24:28

Re:DataEase 8.5 64bit

Hi Marco.

DE 8.5 is only delivered in 32 bit version. 

There is strictly speaking no incentive or reason for us to develop a 64 bit version as it would really only be for showcase that we could.

32 bit versions work 100% in 64 bit while 64 bit versions obviously only work in 64 bit onward. 

If your check your Program files vs. your Program Files (x86) my guess would be that the latter is crowded with software you use all the time and the other one mostly have OS software. (Microsoft).

As there are few benefits and a lot of drawback by moving the code to x64 most software suppliers simply don't.

Here are 10 reasons why not.

1. 64-bit Libraries

Although it may seem like a no brainer, many application upgrades fail due to a lack of 64-bit libraries. A 64-bit application works best with 64-bit support libraries. If you use 32-bit libraries, then you must marshal data between the two environments. That slows down application speed considerably and introduces potential errors. Marshaling pointers can become especially troublesome when the pointer is for something like a data structure, which may not convert well between 64-bit and 32-bit environments.

Most problematic libraries contain custom code or come from third party vendors who add value to platforms such as Java and .NET. However, you also need to exercise care with main platforms. For example, the 64-bit version of the .NET Framework generally resides in the WindowsMicrosoft.NETFramework64 folder, rather than the WindowsMicrosoft.NETFramework folder—a difference that some developers will miss. Open source libraries may require that a recompile to provide 64-bit functionality; try to find a 64-bit download first so that you don’t have to perform the required optimization.

2. Third Party Product Support

Some applications rely on applications created by other vendors. These other applications may not work well with 64-bit applications, or the 64-bit version of the third party product might have compatibility issues. For example, consider an Excel application that accesses eBay’s Web service for the purpose of automating sales. The 64-bit version of Excel isn’t completely compatible with the 32-bit version of Excel, so you might encounter a host of unexpected problems with your application upgrade. It’s easy to miss a problem such as using a 32-bit number to hold a 64-bit handle, truncating it, and causing a crash because the handle isn’t valid.

3. Data Access

All kinds of problems can occur when moving code from a 32-bit data environment to a 64-bit data environment. One common problem is that an 64-bit application that writes 32-bit values as 64-bit values. A 32-bit application accessing the same database will access the same data in 32-bits, with resulting errors. In some cases, the data is completely mangled before anyone realizes that there is a data marshaling problem. When you perform an update, make sure that 32-bit data values are still written as 32-bit values.

Sometimes, the data marshaling requirements can be quite subtle. For example, code from a managed environment such as Java or .NET can call into the operating system. To the managed code, the value still appears to be 32-bits, but the 64-bit operating system call treats it as 64-bit data, introducing a subtle, nearly impossible to locate error. Someone in your team has to trace absolutely every data transaction to ensure that what you think you’re writing as data is what you’re actually writing. Of course, you always test your update on test data, not on production data.

Data issues include both data storage on disk, as well as in memory. Many developers learn the hard way that data structures that work fine in a 32-bit environment no longer work in a 64-bit environment. This particular problem can have many causes, but the main issue is the way the 64-bit environment packs the data into the structure. The data structure uses a different alignment in 64-bits, so that even if all of the data elements are the same size, they aren’t in the same location in memory. Of course, this problem is exacerbated by problems such as pointer size; a 64-bit pointer is twice the size of a 32-bit pointer.

4. 64-bit Programming Rules and Skills

Humans make code updates. It’s something that somehow escapes the notice of planners at some organizations, but it’s a fact that you need to consider. If your coding team lacks 64-bit programming experience, it presents a barrier to performing an application upgrade. For example, team members should be aware of the rules for converting data from 32-bit to 64-bit form, and vice versa. (What’s worse is that these rules are generally unwritten, platform and application specific, and often rely on past experience.)

If you have any hiring responsibility, ask job candidates about their experience in this area. If you’re “just a programmer” and can only deal with the people you’re dealt, pay even more attention because it’s knowledge you need to acquire (and it won’t be bad for your career if the 64-bit expert turns out to be you). If team members lack this sort of information, the resulting 64-bit application will likely contain errors that the team won’t even find. More importantly, the lack of 64-bit programming skills will cost time and money—something in short supply for most organizations today.

5. Operating System Feature Access

It may seem as if a 64-bit operating system would make it easy to access operating system features, but this isn’t always the case. For example, Windows provides an extremely odd method of allowing access to the registry. On the 64-bit version of the operating system, 32-bit applications can suddenly find their keys moved and 64-bit applications may find it difficult to locate data generated by 32-bit counterparts. The solution to this problem (and those like it) is to detect whether you’re working with a 64-bit version of the operating system, and then provide code that looks for the required 32-bit data in the alternate location.

6. Prepare to Tell the Boss: Check Hardware Capacity

A 64-bit application uses data elements that are twice as wide as a 32-bit application. The memory requirements don’t suddenly double, but the new 64-bit application will have bigger memory requirements. Suddenly, the 32-bit application that used to fit just fine in your user’s memory won’t work as a 64-bit application, and the system will run slower – which is exactly opposite of what they expect. As part of the application update, the organization should perform a hardware survey to ensure that the hardware has enough capacity to support the 64-bit environment.

7. Trick Code

Some developers rely on trick code to achieve certain goals, which might include weird hacks to work around an otherwise unsolveable defect. For example, I might add 1 to a 32-bit register until such time as the register overflows and returns to 0 (with a requisite change to the overflow flag). When making the move to 64-bits, such code can break, causing the application to malfunction. It doesn’t matter which language you use; all of us developers have created trick code of this sort. It’s a shortcut to writing longer code that doesn’t execute as efficiently (but often executes more reliably). Before making the transition to 64-bit code, perform a code review to locate potential problems of this sort. The more clever it is, the more carefully you should examine it. The trick code will have to be rewritten to execute more reliably in a 64-bit environment.

Of course, you might suggest that the added reliability causes speed problems. Users see speed; they don’t see reliability. Making the code more reliable by rewriting it to use best practice techniques also makes it more secure. So, you’re trading a bit of speed for enhanced reliability and security by rewriting the code. Given that speed is cheap today and that nefarious individuals are intent on invading your network, the rewrite is at most a tiny inconvenience for a huge payoff.

8. Math

It seems as though mathematical operations should be safe when converting from 32-bits to 64-bits. After all, 1 + 1 still equals 2 whether you use 32-bit or 64-bit numbers. The problem occurs in a number of ways. One potential problem is the issue of sign extension. A value is converted to a signed or unsigned integer, when you actually meant to use the other type of value—the equation 1 + 1 might suddenly become 1 – 1 without your knowing it (this is an oversimplification, but it demonstrates the principle). To avoid this potential problem, your test harness should consider a number of math tests for the converted application that test limits of both positive and negative numbers to ensure the application produces accurate results.

9. Supporting Hardware

Some hardware simply won’t support 64-bit access, and that’s especially so for older hardware. This concern may not affect most business applications, but it definitely affects any scientific application that relies on any sort of external sensor. It can also affect a variety of industrial and specialty applications. For example, consider a security system; you need to know that the cameras will interact properly with a 64-bit application before you perform the upgrade and find that they won’t.

10. Drivers

You might think that driver issues are gone once a 64-bit operating system can access all of the hardware on a system. However, the operating system might rely on a trick to access a 32-bit driver. In some cases, the use of a 32-bit driver causes problems for your 64-bit application. This is especially true for video or other graphics drivers. Consider the problems of accessing a color printer or other graphics equipment if all you have is a 32-bit driver. As with libraries, make sure any drivers you want to access (including things like software sensors such as Geosense for Windows) provide 64-bit access to reduce potential errors, reliability problems, and security holes.

Now you have a definite edge over your peers in migrating 32-bit applications to a 64-bit environment. By addressing these ten basic issues, you significantly improve the chances of your upgrade project succeeding.

However, this isn’t the end of the line. Most platforms and applications require attention to specific upgrade needs. Vendors such as Microsoft are usually happy to help out. For example, check out their suggestions for migrating your managed application. Check out forums as well. Java developers would do well to look at this message thread. Linux developers might want to ask their specific migration questions on LinuxQuestions.org (for example, How to check if linux kernel is 32 bit or 64 bit). The bottom line is that you need to research the upgrade carefully before you begin creating a specification for it and long before you rewrite that first line of code.

...

Product: DataEase 8.5 Runtime

Written by: DataEase

23/05/20 12:46:53

DataEase 8.5 64bit

Hi DataEase, My Company use Player and Developer of DataEase 8.5 version 8.5.1.2674 and it seems to me that these application are both 32bit versions. There's an available version of DataEase 8.5 at 64bit? Thanks

...

Product: DataEase 8.5 Runtime

Written by: Marco Marchesi

20/05/20 12:21:20

1c 8.3 vs DE9

Is there any light at the end of  ...DE9 saga ?

meanwhile have tested russian 1c 8.3 on Catalina 10.15.4 macOS on macbook pro 

no windows emulation ..pure macOS and pure 1c 8.3

the configuration was built from the scratch and pictures were loaded in database ;)

DE9 it is your turn now ...

...

Product: DataEase 9 Developer

Written by: Ihor Zakharchenko

20/05/20 00:59:30

Re:Re:Re:Is there user groups capability in DataEase 8.5?

Hmm..

There is not anything in DE85 Windows version that is built in other than the User Levels etc.

However there is this when you use the Web Server side of things but that is not much help here.

We have made a system like this several times in application where we simply create the structure in tables and either check "user rights" before you open a Document or the document do this in a virtual field/oml and simply give an alert and close.

You can do anything you like in 8.5 but out of the box there is no such solution.

...

Product: Dataease [{8}]FIVE

Written by: DataEase

18/05/20 18:28:28

Re:Re:Is there user groups capability in DataEase 8.5?

Yes, but separate from DataEase user level security infrastructure.

...

Product: Dataease [{8}]FIVE

Written by: Barry Sweet

18/05/20 16:59:06

Re:Is there user groups capability in DataEase 8.5?

Are you thinking access rights etc for groups?

...

Product: Dataease [{8}]FIVE

Written by: DataEase

18/05/20 16:16:45

Is there user groups capability in DataEase 8.5?

...

Product: Dataease [{8}]FIVE

Written by: Barry Sweet

05/05/20 20:29:59

Re:Re:Re:Re:Re:How do I do a count of the number of yes's in yes/no fields

20 relationships is 'ugly' and the counting can be slow if you have a lot of records...

I would create a hidden integer field with a derivation of 'if( fieldname01 = 'yes', 1 , 0 ) for each of the 20 fields.

Then just do a 'sum of tablename fieldname01'

Only 1 relationship needed

...

Product: LegEasy DOS

Written by: Earl Wertheimer

DataEase Mainpage