Buy Support
Incidents |
If you can't find your answer
in the FREE PUBLIC QDeveloper Forum, require URGENT Priority Support, or you need to send us
private or confidential information: |
Click Here
|
If you can't
login and post questions or you are having trouble viewing forum posts:
Click Here
|
Callback
Support |
If you live in USA, UK, Canada, Australia or New
Zealand, you can leave us details on your question and request us to call you back and discuss
them with you personally (charges apply). |
Click Here
|
Buy Support
Incidents |
If you can't find your answer
in the FREE PUBLIC QDeveloper Forum, require URGENT Priority Support, or you need to send us
private or confidential information: |
Click Here
|
|
Release 4.00.23 Fixes |
Author |
Message |
Tom |
|
Group | : Administrator |
Posts | : 5510 |
Joined | : 2006-02-17 |
|
Profile |
|
Posted : 2006-06-21 09:33:13 |
On the setup screen added "Text Field Handling" frame that includes "Convert Fields > 255 to LONGVARCHAR", used if the development environment wants VARCHARS > 255 to be LONGVARCHARS, and "Limit Length To" so a maximum field size can be entered. Some development systems will not handle fields larger than a certain size. (Access Memo max 255, MSSQL Text Field max 4096, ADO Text Field Max 8191.
Fixed issue when selecting less than from a Key Field Order by Accending and the Data contains a NULL value. Not the NULL value will only be accessible with IS NULL.
Changes VARCHAR from "not support" to "is supported".
|
|
|
|
|