4D v14.3
Version type
- 4D Language Reference
-
- 4D Environment
-
- Application file
- Application type
- Application versionUpd
- BUILD APPLICATION
- CHECK MEMORY LEAKS
- Compact data file
- COMPONENT LIST
- CREATE DATA FILE
- Data file
- FLUSH BUFFERS
- Get 4D folder
- Get database localization
- Get database parameter
- Get last update log pathNew
- Get memory leaks
- GET MEMORY STATISTICSUpd
- GET SERIAL INFORMATION
- Get table fragmentation
- Is compiled mode
- Is data file locked
- NOTIFY RESOURCES FOLDER MODIFICATION
- OPEN ADMINISTRATION WINDOW
- OPEN DATA FILE
- OPEN SECURITY CENTER
- OPEN SETTINGS WINDOW
- PLUGIN LIST
- QUIT 4D
- RESTART 4DNew
- SET DATABASE LOCALIZATION
- SET DATABASE PARAMETERUpd
- SET UPDATE FOLDERNew
- Structure file
- VERIFY CURRENT DATA FILE
- VERIFY DATA FILE
- Version typeUpd
- ADD DATA SEGMENT
- DATA SEGMENT LIST
Version type
| Version type -> Function result | ||||||||
| Parameter | Type | Description | ||||||
| Function result | Longint |
|
Demo or full version, 64-bit or 32-bit version, 4D database / Merged application | |||||
The Version type command returns a numeric value that denotes the type of 4D or 4D Server version that you are running. 4D provides the following predefined constants, found in the 4D Environment theme:
| Constant | Type | Value | Comment |
| 64 bit version | Longint | 1 | |
| Demo version | Longint | 0 | |
| Merged application | Longint | 2 | Version is an application merged with 4D Volume Desktop |
Note: In current versions of 4D, the demo mode is not available.
Version type returns a value in the form of a bit field; it is necessary to use bitwise operators to interpret it (see the examples).
COMPATIBILITY NOTE: In versions of 4D prior to 13.2, a different set of constants was available for this command; however, these constants did not handle some cases properly, so they were modified. This modification means that your code must be adapted (see example). However, if you wish to keep the previous functioning, you can just replace the constants in your existing code with their former values: 2 for 64 bit Version, 1 for Demo Version, 0 for Full Version.
Your 4D application contains specific code based on the version running. You can find out the execution environment using the following code:
If(Version type?? 64 bit Version)
// We are in a 64-bit version
Else
// We are in a 32-bit version
End ifThis test lets you run different code depending on whether the version is a merged application or a database opened by 4D / 4D Server:
If(Version type?? Merged application)
// We are in a merged application
Else
// We are in a database executed by 4D
End if
Product: 4D
Theme: 4D Environment
Number:
495
Created: 4D v6
Modified: 4D v12
Modified: 4D v13.2
Modified: 4D v14
Application type
Application version
64 bits
4D Language Reference ( 4D v14 R2)
4D Language Reference ( 4D v14 R3)
4D Language Reference ( 4D v14.3)
4D Language Reference ( 4D v14 R4)
Inherited from : Version type ( 4D v13.5)
