Today we compiled version 1066 of DataEase 7.5. A memorable number, and to be honest quite a memorable version too. For the first time you can now edit and store RichtText (HTML) directly in a DataEase for Windows form.
Development of both 7.5 and DG3 is storming forward and we are looking forward to sharing it with you in the not so far future. We will leave DG3 alone for the moment, and focus on 7.5 a little. It definitely deserve not to share the limelight over the next couple of months, as we now feel certain that it will be a great version of this product and one that the DFW community will really love working with.
DataEase has kept "rigorously" to its database roots, and up till now the only thing you could have stored in our Database has been text and numbers, and the only thing you could have displayed in our fields have been ....you guessed it..... text and numbers. Not completely true, since we have also had the ImageField where you could store a path to an image, and we would then display it in your form, but still this is too close to the truth for comfort.
In 7.0 we introduced the "new" Memofield, and even thought the intentions was the best, it has since been reviled. Partly because it was not without weaknesses, and partly because it didn't really improve the functionality over the trusted old one. Bugs aside, the new Memo field never got a chance.
The funny side to this story, is that it is basically the Memo field and the ImageField , both re-invented, that is the strongest news in 7.5. Up to now, the link between the form and the table has been rather rigorous in DFW, but in 7.5 we tear them apart and say that what is stored in the table, and how that is represented in the form is not the same. The idea come from the ImageField, where what is stored is really just a normal textfield, but what is viewed is what that is derived too as an image.
In 7.5 we have made to representation of a WebField i.e. a field that display a Web Browser object in a DFW form. A WebField on top of a Textfield, is interpreted as a URL, and the derived URL is loaded in the control. If you build a WebField on top of a Memo field, the content of that Memofield is read as HTML i.e. you can store encapsulated HTML in the Memo and the result will be displayed as a WebPage/WebObject in your form.
So what possible use can this be? Your imagination is the limit. You can use it to view any webpage, or you can use it to view a dynamic header on your forms, or you can use it to view a graph, a chart, a film, a calendar....you tell me!
Published: 17/04/12 - 19:43:09 (Amanda Higgins)
Last changed: 30/04/12 - 15:54:01 (Ulrik Jacob Hoegh - Krohn)
New server? Settings to check on 2003 and 2008.
With new versions of operating/server operating systems, there is always new challenges. We have currently tested DataEase on 2008R2. This work also brought light on problems that has been with earlier versions of Windows server, so please find below a re...
The DQL body Layout of Despair
Do you recognise this? If you do, you are not the only one. In 7.5 our focus is on moving DataEase for Windows into the 21st Century, but instead of attacking the core product - that is called DataEase Generation 3 - we try to include new functionality th...
LegEasy 6 Windows aka 6.53 . New version. Build # 3150 Released: 16.05.2012
LegEasy 6 Windows (6.53) is the first step on the ladder towards the new DataEase. Our focus is not to allow you to maximise the value of your existing applications, when at the same time you will be able to move forward onto the web and out into the worl...
Windows 2008R2 Server and DataEase LegEasy 6 (6.53)
6.53 has now been out for 3 months, and it has been very few reported problems. No software, old or new will or can be released without some problems being reported. The intentions behind 6.53 was to create a "modern" version of DataEase 6, but without c...
Wait for Eight! - DataEase 8, not the other one...
We know that a lot of DataEase 6.x users, have tried migrating to DataEase 7.x, and for variable reasons this has not been a success. In the early days (7.0 and 7.1) the problem was that 7.x was still a immature product, and later when things stabilized i...