FlexODBC users, application developers and product engineers now have a Technical Support HelpDesk (www.QDeveloper.com.au  Forum). Here everyone can participate in technical discussions, share, advise, post support queries, report product bugs, search the FAQs and much more.

E-Mail Support
Post questions to us by e-mail and we will try to get your question resolved quickly. Send your support emails to support@DataAccess.com.au. Please make sure you have included the Serial Number of your product. One-to-One Email Support issues will be subject to a A$33.00 per incident fee.

Announcement List
To be alerted to news about FlexODBC, product releases, beta test cycles, new features and promotions:

Data Access Worldwide Support Solutions

We offer a variety of technical support solutions in order to give our customers a wide range of choices to determine how we may best help them meet their support needs.

Our FREE QDeveloper Forum
Our FREE forum is dedicated to the professional exchange of information where QODBC & FlexODBC users can post support queries, report product bugs, search the FAQs and much more. To visit the forum 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, purchase one of our Support Incidents by clicking here.

Callback Support
If you live in the USA, UK, Canada, Australia or New Zealand, you can leave us your contact details with your question and request us to call you back and discuss them with you personally (charges apply).

Pre-Paid Phone Support
Pre-Paid Phone Support time must be purchased from our website prior to placing a support call. Telephone support is the fastest way to speed up problem diagnoses and resolution or simply receive an experienced perspective on your particular issue. Telephone support is billed at the rate of A$33.00 per 20 minutes for one question or issue ("incident"). After you have purchased support time, you will be advised of the priority support number to call to speak to a technical support person or to make an appointment. While there are times the technical support team will be available for immediate help, they may have other calls to handle before scheduling your time. We will attempt to close all calls the day of your call.

FlexODBC Errors

There are many different types of errors returned by ODBC. The most common of which is the generic "Syntax Error". This typically means that your SQL query could not be parsed, possibly because of one of the following types of errors.

There may be other syntax related errors we are not yet aware of. Syntax errors are always an SQL related problem, not a problem with the DataFlex DBMS file system itself. If you manipulate files directly via SQL, you may want to purchase a book on SQL to use with this product. The FlexODBC manual does not provide adequate reference to SQL syntax.

Dates
Dates in FlexODBC are returned in the SQL standard date format of 'YYYY-MM-DD'. This format allows proper sorting from all environments.

In the control panel there is a setting for the number of digits to use for the years of dates. You should set this to match your system and tell the driver if you use 4 or 2 digit year format. This will affect correct operation of comparisons of date values.

A typical date related SQL statement would look something like this: select * from small where date < {d '1996-05-27'}

Note: According to ODBC rules, NULL dates (where no date has been entered) are not included in queries where a specific date comparison is requested. In the above example, dates less than the date requested will be shown, but records without a date entry (null dates) will not be included, unlike DataFlex operation. You can select these records specifically by modifying the query to: select * from small where date < {d '1996-05-27'} or date IS NULL

Multi-User
FlexODBC v4 is not user counted and therefore is Multi-user by default. If you are unable to open a DataFlex file in the Single User version of FlexODBC 2.5 or 3.1, it may be because the driver opens files in "exclusive" mode for this license. If you are running on a network, you will need the Multi-CPU or User-Counted version of the product to open shared files on a network.

Tracing
A tracing mode has been included in the product. It allows you to trace all ODBC calls made to the driver for debugging purposes. A trace log may be required by our support staff if your application returns an unexpected error.

To trace operations, enter an ASCII filename to the driver setup screen under the ODBC icon in the control panel. A name such as:-
C:\flexodbc\dftrace.log

Tracing in this example will be sent to an ASCII file called c:\flexodbc\dftrace.log. The trace includes all ODBC calls made and DataFlex DBMS related errors returned by the driver. If you cannot see the problem, e-mail it to us for review. Program anomalies will be addressed at no charge and updaters posted on our web site. Other support issues will be subject to a A$33.00 per incident fee. Send your support emails to support@DataAccess.com.au. Please make sure you have included the Serial Number of your product.

FAQs
Most common support issues are also covered in our FlexODBC Frequently Asked Questions and Solutions for the DataFlex Embedded DBMS web page and within the FlexODBC Manual installed with the product.

DataFlex Error Codes

Some of these errors may possibly occur when connecting FlexODBC to DataFlex Embedded DBMS Tables. Others may occur when running your DataFlex Application "Program code". Please consult your error code for the recommended action or explanation before contacting support.