General Info on Vista Security modes and Manifest files - includes basic information on the new security settings in Windows Vista.
How to run dBASE Plus IDE in Windows Vista - includes the best way to set up dBASE Plus to run in Vista.
How to run dBASE Plus executables in Windows Vista - includes the best way to set up dBASE Plus deployed .EXEs to run in Vista.
Visual Issues - includes examples on the visual differences of dBASE Plus objects in Vista vs. XP.
Performance Variations and Issues - includes examples of the differences on some dBASE Plus properties and methods in Vista vs. XP.
Manifest File Samples - Download samples of Manifest files for dBASE and the BDE.

In Windows Vista, Microsoft has made substantial changes in how Windows handles security when starting a program.

In older versions of Windows, programs ran all the time with whatever security level the logged in user possessed.
In addition, it was possible to startup Windows with a workstation only login that, by default, gave the user full access (i.e. administrator access) to everything on a workstation.

In Windows Vista, Microsoft has substantially tightened security as follows:

• Vista defaults to running a program with a fairly low privilege level even if the user logs in with a higher security level.



• Via manifest files or embedded manifest resources, Vista can be told the privilege level a program requires, in order to run properly.



• The action Vista takes when a program attempts to perform an action that requires elevated privileges can be configured via workstation or domain level security policies to:

1. Prompt a user to login with elevated rights or administrator level rights when needed
2. Terminate a program that attempts to perform an action that requires higher level rights
3. Automatically elevate a program to a higher level if the logged in user has sufficient rights

More detailed information about Vista security and other compatibility issues is available at:

http://msdn2.microsoft.com/en-us/library/aa480152.aspx

Generally, setting the requested execution level to 'run as Administrator' will allow existing dBASE and BDE Admin executables to run properly.

There are two ways this can be done :

1 - Using the Manifest file's 'requestedExecutionLevel' setting.
dBASE Plus can be run successfullly on Vista by installing the application manifest file that contains the appropriate requestedExecutionLevel setting. The BDE Administrator must also have a manifest file installed for it to run on Vista.
(NOTE: dBASE Plus installers from version 2.61.4 on up will automatically include the Vista manifest files )

Instructions ...

All Manifest files must be installed in the same folder as the executable it is intended for.

The 'Administrator rights' manifest files for dBASE can be downloaded here :
http://www.dbase.com/Manifests/ManifestAdminRights.zip

Save the plus.exe.manifest file in the same folder as the plus.exe file
(Default folder is C:\Program Files\dBASE\PLUS\BIN)

Save the plusrun.exe.manifest file in the same folder as the plusrun.exe file
(Default folder is C:\Program Files\dBASE\PLUS\Runtime)

Save the bdeadmin.exe.manifest file in the same folder as the bdeadmin.exe file
(Default folder is C:\Program Files\Common Files\Borland\BDE)

NOTES:
It is recommended that you re-boot your computer after adding the manifest files

When you install dBASE Plus (from dBASE Plus version 2.60 ... up to 2.61.3) a Manifest file is automatically installed under the bin folder.
This Manifest file has the settings to allow the use of the Version 6 common controls in Windows XP (and Vista).
If you already have this file make sure you delete it before installing the replacement Manifest file since the Vista manifest file will also include these settings and you do not want to accidentally rename the new manifest file.

Vista Manifest files are not compatible with XP operating systems.

------------------------------------------------------------------------------------------------------
Example: If you'd like to take a look, This is what the Vista Manifest file for Plus.exe looks like.
(Note: the section in blue has the 'requiredExecutionLevel' setting required for Vista)
-------------------------------------------------------------------------------------------------------

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0">
<assemblyIdentity
   version="1.0.0.0"
   processorArchitecture="X86"
   name="PLUS.EXE"
   type="win32"
/>
<description>PLUS.EXE Manifest</description>
<dependency>
   <dependentAssembly>
      <assemblyIdentity
         type="win32"
         name="Microsoft.Windows.Common-Controls"
         version="6.0.0.0"
         processorArchitecture="X86"
         publicKeyToken="6595b64144ccf1df"
         language="*"
      />
   </dependentAssembly>
</dependency>
<trustInfo xmlns="urn:schemas-microsoft-com:asm.v3">
   <security>
      <requestedPrivileges>
         <requestedExecutionLevel level="requireadministrator"       uiAccess="false"/>
      </requestedPrivileges>
   </security>
</trustInfo>
</assembly>
------------------------------------------------------------------------------------------------------

2 - Using the .exe's 'privilege Level' setting.

Instructions ...

Right click plus.exe (Default folder is C:\Program Files\dBASE\PLUS\BIN)
- Choose 'Properties'
- under the 'Compatibility' tab .. 'Privilege Level' setting
- click on the checkbox next to 'Run this program as an administrator' to turn it on.

Right click plusrun.exe (Default folder is C:\Program Files\dBASE\PLUS\Runtime)
(follow instructions for plus.exe)

Right click bdeadmin.exe (Default folder is C:\Program Files\Common Files\Borland\BDE)
(follow instructions for plus.exe)

Windows XP SP2 compatibility mode
Another option that is available on Vista is the 'Windows XP SP2 compatibility mode'.
This is created to prevent the "This program might not have installed correctly" dialog box that shows for applications that are hard coded to look for the XP version.
If you are installing from the plus-setup.exe file then you should set the 'Windows XP SP2 compatibility mode' as detailed below for the plus-setup.exe file.

Also, The bdeadmin.exe file should be set to use the 'Windows XP SP2 compatibility mode'. If you do not set the 'Windows XP SP2 compatibility mode' for the bdeadmin.exe, the manifest file (bdeadmin.exe.manifest) may be ignored when trying to run the BDE Administrator. This may cause any changes to be saved incorrectly when modifying the BDE Config file directly.

Right-click on an .exe name or shortcut - goto Properties - under the Compatibility tab - apply the Windows XP SP2 compatibility mode.

OR

2. In Internet Explorer from the Toolbar goto Tools | Internet Options. Under the 'Security' tab highlight the Local Intranet section. Click the 'Sites' button. Click 'Advanced' and add the server's address to the list of trusted zones.

TreeView object - In Vista the TreeView object does not adhere to the foreground portion of the colornormal property. In XP it does.

ScriptMaker - If you are using ScriptMaker ... the icons on the pushbuttons and on the toolbar are all white. There is an outline shape of what is there. But, no detail in the icons. However, with the new release of dBASE Plus (2.61.2) a new Inno script maker called 'Inno Script Generator' is included. So far this application does not show any issues related to Vista.

HELP System
Microsoft has released a Windows Help Program (WinHlp32.exe) for Windows Vista. This will allow Vista to display 32-bit Help files that have the ".hlp" file name extension.

Click Here to download this program.

dBI is working on support for HTML Help in an upcoming release of dBASE Plus.

Open File or Get File
In any get file or open file dialog, the 'Look in' drop down list does NOT show the current folder until you choose one. Goto File | Open in the main IDE menu. Or Use GETFILE() function to see this behavior.

ScriptMaker
NOTE: if you are using ScriptMaker ..
after opening a scriptmaker project - the moment the hScrollBar is moved to see the top 'Inno' Compiler button, this error comes up...
Scriptmaker (title)
Integeruberlauf.