I have just downloaded DataEase 8.2 and is trying to use the Startup.exe to start one of my applications directly from the catalogue. 

Nothing happens, any idea what is wrong?

Startup.exe depend on paths and environment variables set up at installation of DataEase 8.2. These settings are only done by the FULL version of DataEase 8.2 and only in versions higer than 1594. (8.2.0.1594). If you run an older version of DataEase 8.x it will not work!

How to find out if these environment variables are set correctly:

1. Simply go to DOS and type DataEase. If DataEase 8.2 starts automatically the environment variables are set correctly.

2. If it doesn't start, the problem is most likely that you don't have enough rights to set the environment variables when you install software. Try running the installation again, but run it as Administrator. Try 1 again after installation.
3. If it still don't work you can check the Settings and see if any changes was made by the installation software. You find the settings in the control panel:Control Panel\All Control Panel Items\System

The variables set should be DEPROGRPATH and it should point at the installed DataEase 8.2.

if this is missing the installation failed due to lack of access rights on the user that did the installation. Get an administrator to perform the installation for you or try to run the following program found in the DataEase 8.2 program catalogue:

DESetPath.exe

NB! Remember to run it with Administrator Privileges. After running it, perform the tests above again.

I successfully installed on my client the last version of DE8 (8.2.0.1600) recently released.

I tried to use the new function “startup” downloading the simple tool for the website.

Putting the unzipped file in anyway directory “startup” works fine and the database is opened.

Here the ini file provided :

[STARTUP]

AppPath=.

AppName=FormVirtualTest

UserName=User

Password=User

But where’s located the database? I didn’t find it. I mean: where I find the file .DBM .TDF .FRM etc of the Application FormVirtualTest ?

But it works!

Anyway..

Then I tried to use “startup” with one of my databases copying the files .exe and .ini into the directory of the database and “startup” works fine.

Here the .ini file used :

[STARTUP]

AppPath=.

AppName=PRAGMA

UserName=high

Password=high

Then I tried to use startup with another database copying the files .exe and .ini into the database directory but the “startup” doesn’t works.

Here the .ini file used

[STARTUP]

AppPath=.

AppName=Bonding Italy

UserName=high

Password=high

Here the system message received:

I suppose that “startup” doesn’t support a database name with a blank character inside the name.

I tried to insert a double quote for the application name but it doesn’t works again and the system reply to me the same message.

I tried also to insert a single quote for the application name but it doesn’t works again and the system reply to me the same message.

AppName="Bonding Italy"

AppName=’Bonding Italy’

There’s perhaps some trouble within DataEase using a Database Name with a blank character inside the name?

There’s perhaps a character limit for the database name ?

Take in mind that our shortcuts to the databases works fine.

Here the target of the shortcut:

"C:\Program Files (x86)\DataEase\DataEase 8.1\DataEase.exe" W:\dwh_sic "Bonding Italy"

Thanks a lot for your time.

Hi Marco.

I am glad that you have both started to play with the new feature and that you give us feedback on its shortcomings ;-)

What you see here, Startup.exe and the new release today 1602 with ALWAYS able to switch to Design Mode is the beginning of a new proper split between Design/Development and Deployment/Runtime.

Startup.exe is currently in 1.0 with a lot of weaknesses, so we are already making 2.0

2.0 will:

• 1.Work without Startup.ini, so if you have no startup.ini it will read RDRR and start the application in the catalogue with Login dialogue.

• a.It will start Runtime if Runtime is installed, or Development if Runtime is not installed.

• 2.If Startup.ini is present, it will work the same as Above, but you will have an exstra switch where you can decide if it should start Developer, Runtime or Give you a dialogue where you can choose.

• 3.The spaces in path/app name etc, is a classic Windows problem. DFW doesn?t use the windows method, but Startup.exe do so we simply need to make some more checking and this too will work.

The reason you can?t see the application files is because they are hidden. This was a test for Deployment/Runtime as we don?t want users to have a relationship with the Application files.

When this split come full circle the deployed application will never be touched by a developer version of DataEase. It will be encrypted and packaged, and the Developer will not be ?able? to work directly on the app. Changes and updates will be handled by the deployment server, and all development and changes will happen in the development environment.

Download New Startup.exe

This version of Startup.exe will handle Application Names with space in them.

Simpley but the application name in ""

AppName="Space In Name"