| Q |
I have downloaded the 32-bit Paradox File Driver but I'm having difficulty registering it in the Clarion IDE.
|
| A |
The Clarion IDE currently only registers 16-bit file drivers, so you must also download and install the 16-bit Paradox File Driver.
You must also install the 16-bit BDE supplied with the Paradox File Driver.
|
|
| Q |
Do I have to purchase both the 16-bit and 32-bit Paradox File Drivers in order to develop 32-bit apps?
|
| A |
Since the Clarion IDE can only register 16-bit file drivers, you must install both 16 and 32-bit versions of the Paradox File Driver when developing 32-bit apps.
However you only need to purchase one key to unlock both 16 and 32-bit drivers and all subsequent updates at the same version.
See our Suppliers page for more details.
|
|
| Q |
What versions of the Borland Database Engine are supported by the Paradox File Driver?
|
| A |
The 16-bit Paradox File Driver was developed using BDE 2.51 which is supplied with the driver.
However the driver has also been extensively tested under BDE 2.52 which is the latest (and final) 16-bit version of the BDE.
The 32-bit Paradox File Driver has been tested under BDE 3.5.
|
|
| Q |
Can I use Meta Properties with the standard Clarion File Drivers?
|
| A |
No. Although the Meta Properties are a layer within the TopSpeed File Driver Kit, this layer must be compiled into the File Driver.
The standard Clarion File Drivers do not currently have Meta Properties.
|
|
| Q |
The driver displays an annoying popup window every time I run my application.
How do I prevent this from happening?
|
| A |
The final release version of the driver will display this screen until it is registered using the L3REG application.
The beta version of the file driver cannot be registered, so the screen cannot be removed.
|
|
| Q |
I have defined an auto-increment field in my Paradox table using an augmented field definition, however I cannot update the value.
What is going wrong?
|
| A |
The Paradox File Driver lets you define a Paradox AUTOINC field using an augmented field definition.
This works slightly differently from using the Clarion templates to do the auto-increment in that the value is determined by the BDE run-time not the Clarion templates.
However, Paradox AUTOINC values are read-only and may not be updated using the BDE.
For this reason the Paradox File Driver ignores attempts to write a changed value back to the table.
If the driver did not ignore such update attempts, the BDE would report an error and furthermore it would complicate the use of CLEAR() to clear the contents of the record.
|
|
| Q |
When I try to use the beta/evaluation version of the Paradox File Driver, a message box appears with an error message like:
Error (n) validating registration data.
What is wrong?
|
| A |
This dialog is displayed when the driver fails when checking the registered user data or driver requirements at load time.
The error number indicates the precise problem which may be one of the following:
| 0 - |
No error, however the driver evaluation has expired.
You should register the driver you have using the L3UNLOCK.EXE application.
|
| 1 - |
A consistency check on the registered user data failed.
This indicates a corrupt driver that may have been tampered with.
|
| 2 - |
The key used to register the driver is incorrect.
Should never occur.
|
| 3 - |
The Clarion IDE is not loaded.
Unregistered copies of the driver require the Clarion IDE to be loaded.
|
| 4 - |
The .LIC file which was installed with the driver cannot be found.
Unregistered copies of the driver require the .LIC file to be present on the PATH.
|
| 5 - |
An error occured processing the .LIC file.
This indicates a corrupt .LIC file that may have been tampered with.
|
| 6 - |
An error occured validating the driver against the .LIC file.
This may indicate a version mismatch between the .LIC file and the driver.
|
|