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

Download Sample

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

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

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

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

don’t worry … simply keep in mind and take that story about CP/M and IBM and OS for the first IBM PC  into account… Glory to DataEase team nevertheless ! 

Thank you for your suggestions. I tried all of them, except trialling DataEase 9x, without success. At this stage of my later years of age, I did not want to move to a new platform. 

However, I did learn that MS had fouled up their updates yet again last Friday. My problem only started after I accessed DE7 following that update, and it continued after the first "emergency update" released by MS on Tuesday, which I had installed. When I learnt of another "emergency update" on Thursday, I waited until I could install this and then once that was completed, I tried to open my DE program again - and it worked the first time".

Since then, during the following 36 hours, I have rebooted my PC a couple of times and opened my DE7 files again, without a problem.

The sloppiness of Microsoft has yet again wasted a lot of my time - and, of course, those of you on this Forum also. Sorry.

Hi All! It seems to me that log files or even dumPs are looking like coding directly in 0 and 1 via engineering panel as it was in ancient times ;) New DataEase approach gives me the way to make forms tables dqlS printing outputs and etc. to get info needed from data … as it was in DFD Golden Age . Web or AI or something unknown now … it means nothing to user. Client needs info from Data and wants to get it Ease .. wish great success to DataEase this way! 

With a very old, many versions app, orphan code & forms tend to occur.

Application\Status is good to use to sort out and clean this up but some error messages do not give much info on where the error is.

Can it be set to write these errors to a log file which hopefully has detail of what form/table/action etc. was being processed when the error occurred?

Curiosity killed the cat and all that. ;-) Most of our install packages never see the light of day i.e. is never published for the general public. We use and test them internally so we can get the best result in the end.

At the moment one of our projects is to make a DataEase portal where one can run DataEase in the cloud "native". We already have dataease.cloud which run a RemoteApp (RDP) solution via HTTPS but its a little "cumbersome" to use RDP so we are looking into better ways to run a Windows App like LE9/DE9/L4D in the cloud.

RemoteEase.exe is built in paralell with DataEase.exe and is basically the same if you don't have the RemoteEase einvironment that will run it via a browser rather than on your computer.

Our main goal for all LegEasy products is to allow existing users with big legacy application of which there is much, much more than one would think to continue using their legacy investments while opening up the applications/databases to web/apps and integration with just about anything via REST API.

Anyone that has set up a Micorosoft SQL server, a Web Server, a Mail Server or anything else know how complicated it all is and how unlikely you are to get it working unless being heavily committed and invested.

The point of DataEase is in the name, to make hard stuff easy (whcih argueably hasn't been true for a long part of the DFW era) but this is where the future for DataEase lay - making hard stuff easy again.

The time where self hosting big applications yourself is behind us. Now you just want to buy the service and be able to expand/add to it at will without having to buy the hardware/software and try to glue it all together.

RemoteEase will not be sold as an installable solution but just as a cloud service where you can then immediately open up your app via REST and build web/apps etc. on top while all your users will get access to the legacy application to via a web interface they can use on thei iPad, PC, Telefon etc.

remoteease.exe behaves the same as dataease.exe.

If you logon with a startup doc as required for user access, then on logout there is prompt if want to logout.
If "OK" is chosen then it logs out.

If "CANCEL" is chosen then it opens the the app in developer mode and the user has full designer catalogue access.

This implies it is the similar to dataease.exe that can only be used for Developer access.

Thx a lot for Your reply! 

There  is no trial or testing serial for 7.2. Its just a legacy download.

If the users are set up in the application with login that will allow the Developer access you need to install the DEPLAYER distribution and use that instead.

LE9 can be installed/copied to server and used like DFD without the need for installation on each device. There are no dependencies to be installed on each device.

From 9.0.7354 we have changed how DataEase read the license number as well so the license number to be used on an app can be inserted into the RDRRxAAA.INI or in DATAEASE.INI etc

DE: extend initLicense to check ini files for licenses. This is the new order of how it is done:

1. RDRRxAAA.INI or RDRRxAAP.INI if player and it exists are checked for [LICENSE] Key=the licensekey for this application and if it exists, a key file is created in app directory

2. programappdata (ex. C:\ProgramData\DataEase\LegEasy 9 Developer) is checked for a file and if that exists it is copied to userappdata (Ex. C:\Users\Administrator\AppData\Local\DataEase\LegEasy 9 Developer) if there not already are a key file

3. App directory

4. Dataease.ini or deplayer.ini if player is checked for [LICENSE]Key=the global license key and if it exists, it is written to userappdata

5. userappdata

6. programappdata

7. the exe that started this programs file path

8. if none of the above, license path is set to programappdata and a license dialog is shown

This means that there will be no need for setup or copying of files and DataEase can be updated in one location.

RemoteEase.exe will allow LE9/DE9 to be run "natively" on a server and accessed via Web browser with the correct distribution. 

It is only included in the distribution for internal testing and will make no difference if used without the correct setup/distribution.

Hi All! https://www.dataease.com/static/files/DataEase-7.2.3.947.exe  What serial # needed to test ? Glory to DataEase Team!

Our guess is that your virus software has blocked some of the files in DataEase 7.

Check your virus software/firewall etc. 

In Windows 11 there is also a Smart App Control which is very invasive. It is there to protect yourself from yourself.

Its a DNA feature in WIndows 11 and can only be enabled from a clean install of WIndows 11 and if switched off it can never be enabled again as your OS then already might be "infected". 

I don't think this is Smart App Control but rather your anti-virus that is "hyper active".

As long as you have your app you don't loose anything. 

Download LE9 from here, you should be able to migrate the app quite easily and see if you get the same problem.

You get 30 days trial so can use it to see what the problem is.

Thank you for your prompt reply.

I had considered all the ideas you suggested before sending in my query. However, my version of Dataease was a slightly earlier version than the one you sent the link to, so I uninstalled my version, ran an app that wiped all vestiges, and then used the link you sent to install the later version. This worked, and I was able to open my application. I spent as much time as I could copying data into Word and Excel files last night, just in case I lost access again. I also closed and reopened DataEase three times, without any problem. 

I tried to open Dataease again this morning, without success. I repeated what I did yesterday, again without success this time. However, I read later this morning that last Friday's and Tuesday's MS Windows 11 updates were flawed, causing some applications to fail to open. As instructed, I updated Windows with yesterday's W11 update, then repeated yesterday's reinstallation of Dataease. Again, it has failed. It hangs when I get to the username and password entry. I tried to open Club Paradease from the samples, with the same outcome.

I have checked that the database hasn't moved:

As you can see, the relevant files were last used at 23.10 last night. What I can do this morning is create a new application that opens in Designer mode (see attached file). 

So, is there anything else I can do? Thankfully, I can now view all my historical data, but I can't update it. 

Thank you for the detail.

So for LE9 7342 it must be used similar to DE8.5 where there is a clear separation between developer (dataease.exe) and user (deplayer.exe) logon.

What is the purpose of 'remoteease.exe"?

Long time since anyone around here has started DataEase 7(2) sow as a little weird to try it, and it was hanging for quite a while (compared to LE9/DE9) before starting up.

If memory doesn't fail me, DE7 do a big NETBIOS search to find other DE users before opening up an app and that way of looking up network user is obsolete so it fails before it open the app (this was removed early on in DE8). 

There is nothing that has happend with DE7 but obviously it will get more and more obsolete as times pass. Possibly MS have done something that DE7 doesn't agree with.

You can try to re-install it to see if it helps as MS do a lot of deleting and it might also be an update to your antivirus software that block some files.

Download below.

https://www.dataease.com/static/files/DataEase-7.2...

I have been a DataEase user since 1982, when it was called DataMaster, and am directly responsible for at least 9 other businesses purchasing the application through me. 

I have been retired for over 20 years and now use my DE application only for me to manage my investments, updating my current database regularly and deleting data for those sold. I have not needed to go into developer mode to change applications for more than 10 years. I bought a new PC last April and a new laptop in January, installed Dataease without problem, and updated my data successfully on December 31st. I used the application without difficulty during January.

Over this last weekend, I tried to update the data. I have been trying to log in to the application several times on both machines, but have been unable to do so. DataEase opens and shows the application list. As soon as I click the application (it is now the only one in the list), it "hangs" on the next page after I enter the username and won't accept the password. 

I then had a brainwave and tried again on my old laptop, which hadn't been used since January. It has not had any updates since then, and I was going to wipe all my data on it and do a factory reset of the HD this Easter weekend. Fortunately, I didn't do this earlier as I have managed to get into my DataEase application a few times since Sunday, but this has been intermittent.

Can someone please explain to me what has happened? I have noted that there has been some Forum activity about a similar problem with a later version of DataEase, and solutions have been offered. Can I have the same, please?

deplayer.exe will be as robust and suited for running applications as developer.exe, and possibly even much more robust. 

The goal is to make a proper runtime evinronment where the developer can tailor the application completely and remove all "default" menus/look etc. to produce a proper installable vertical application.

By completely seperating the Developer Environment from the player environment a lot of hybrid problems can be avoided and the platform would be more secure from a development viewpoint as well from a runtime viewpoint.

One problem with Dataease application has been protection of IP as applications could easily be copied/code viewed/stolen if the code hasn't been encrypted which it normally isn't.

Moving forward the code can be protected and even only opened/read by the developer (both person and key) if that is the wish from the developer.

The player that is shipped with DataEase Developer is there for testing how the app will look in player mode.

There is now a lot of seperate configuraiton possibilites for apps in Player Mode.

Player files

When deplayer.exe starts up, it will check for spesial files that is only for player, and if the files are not found, it will revert back to the files used by dataease.exe.

By default player will start in silent mode, that is close if no application are found or the application starts with error code or the application with given user have no startup document. If prism return a error code, this will be returned by deplayer.exe when starting up, and can be read by the shell function starting it.

installdir is the name of the directory deplayer is started from. If deplayer.exe is installed in "C:\Program Files (x86)\DataEase\LegEasy 9 Player" then installdir is "LegEasy 9 Player".

The %appdata%\..\Local\DataEase if put in file explorer will show you all dataease files managed by the current user.

The %programdata%\DataEase will show where other shared data is stored for all DateEase applications istalled for all users.

When opening a application from command line repositoryname is scanned for % and if there is any the environment strings are expanded.

Then we have different routes depending on if command line is with /s for silent or not and if a username/password given together with repopath and reponame.

Normal startup

Check if repo need upgrading and show dialoges for that
If blank user/pw given test for use of external login by first look for login.html in repo path and then in installed app path.

With login.html

Check if auto login is allowed by [STARTUP] AutoLoginPlayer=1 with default 0
If autologin is 1 try to login with blank/blank ot the DEUSERNAME/DEPASSWORD read from enviroment and if not show login.html
The login.html used a new mode on action eIDA_OPENAPP (21240) that can take a json string for setting app data used for login. When the json string is used, openapp switches to silent mode and only return error codes where 0 is success and 203, 205 and 210 is wrong username/password codes. When 0 is returned, the login service windows is hidden and the app is automatically opened.

With normal dialog based login

Check if auto login is allowed by [STARTUP] AutoLoginPlayer=1 with default 0
If autologin is 1 try to login with blank/blank ot the DEUSERNAME/DEPASSWORD read from enviroment and if not show login dialog

Silent startup

Repo is then tried opened by what is given on command line. In this process before trying to open repository, a look for valid license file is done.
First we check %programdata%\DataEase\installdir for a file named $4tp$.key and if found move it to %appdata%\..\Local\DataEase\installdir
Next the repository directory are checked for a license file
Next the %appdata%\..\Local\DataEase\installdir is checked
If no license found in any of there places, %appdata%\..\Local\DataEase\installdir is set as license path and a dialog asking for license if shown.
Last a license validation is done with the following info page in a browser is shown if not valid.
Opening of repos is done with given info, if username/password is not given or incorrect, a dialog/webpage is shown for login.
Temp files are deleted if no errors in startup.

Glad you got it fixed.

There is some recurring "challenges" over the years in DataEase like Sequence Numbers etc. And obviously Date is also one of these.

Originally this was decided by DataEase i.e. what you set in your Configuration file/how DataEase was set up with nice additions to the challenge with things in ZTERMDEF, CONFIGUR.DAT, PRISM.INI etc. 

At some stage in DE6/DFD 5 it was temporarily decided that the Windows version should decide the stored format in DataEase.

When one look inside the code of DataEase one find that the same problem has been solved many times in very different ways simply because many different teams have worked on the product without the hand over being "exhaustive". 

A lot of things that the DataEase "community" has wanted has been almost completed in the code and then abandoned for reasons only the "dead" will be able to answer.

One of these easter eggs is the problem with Date formats in DFW 6/DFD5. We find that migrating DFD 6 mostly works if one "pretend" the application is American and then fix the date problem after migration.

Got it sorted.
Was an issue with the Configuration DBM.
Replaced it and date format is now as expected

Got a very weird issue with an app originally migrated from DE6.53 on both DE8.5 and LE9.

The updated app must be setup for a client with a different regional date setting.

Normally if the regional date format changes then DE will automatically use the new Windows regional settings date format.

The original regional short date setup is YY/MM/DD ; long date YYYY/MM//DD.

The new short date setup in Windows regional settings is DD/MM/YY ; long date DD/MM/YYYY.

For the migrated app any forms with date fields retain the original YY/MM/DD.

Note that this is not and issue with old existing data. The migrated app installation is stripped of data. 

The date field hint in Designer view show the date fields with the original YY/MM/DD format despite being on a server with regional settings short date format DD/MM/YY.

Even if a new form is created in the app the date fields default to the original YY/MM/DD.

If a new app is created on the same server, then date fields have the expected format - DD/MM/YY .

What is causing the migrated app (DE8.5 & LE9) to retain the original location date format YY/MM/DD independent of the Windows regional settings DD/MM/YY?