Support

Troubleshooting

Table of Content

Table of Content

Table of Content

Unable to display table information

This section applies if you got past the signon window but AQT fails to correctly show tables and the information about them.

If AQT is getting errors while trying to get this information, they will be written to the Status Bar at the bottom of the window (if the message is too big to fit into the Status Bar, clicking on the message will display it in full). These messages may shed a light on the problem.

There are two things you can do to try and fix the problem.

Switch off System-Table Queries

The problem could be due to errors while processing the system queries. These can be switched off by:

  • logging off the database (back to the Signon window)

  • selecting Options > General Options > Table Info. Select Use ODBC.

  • logging back onto the database.

This will cause AQT to operate in a more basic mode. This works OK with all databases we have tested it with. You can still access tables and run queries. The only things which will be absent are the system-table queries and some of the DBA tools.

Switch off Parameters

You might try this instead of the previous item.

If you are getting errors while processing the system queries this could be because you are using parameters. A number of databases have bugs in this area.

select Options > General Options > Parameter Usage. Select Use Substitution.

this change comes into effect immediately; you do not need to log off/on.

There is a technical discussion on this subject in Parameter Usage.

Stored Procedure problems with Sybase

AQT sometimes has trouble running Sybase stored procedures, depending on:

  • the version of Sybase you are accessing

  • the ODBC driver you are using

  • whether the ODBC stored-procedures have been implemented correctly in the Sybase Server

The problems AQT has with stored procedure are related to the way AQT determines the parameters for your stored procedure. To get this information AQT uses the ODBC function SQLProcedureColumns. AQT is dependent on this function to work correctly, however for some Sybase implementations this function gives wildly incorrect information. Even on systems where this function works most of the time, it occasionally gives the wrong information.

The Sybase ODBC driver implements the SQLProcedureColumns function by a stored procedure which gets installed on your Sybase Server. This procedure will be installed by your system administrator as part of the setup of the ODBC driver software. If you are having trouble with Run Procedures, you could check with your system administrator that this procedure has been set up correctly, and is the correct version for your ODBC driver.

AQT offers two mechanisms for dealing with these problems:

  • in the Run Procedure window you can change the parameter type (IN/OUT/INOUT) if it appears to be incorrect (the parameter type is main thing the Sybase ODBC Driver seems to get wrong).

  • if your parameters are wildly inaccurate, you can specify that SQLProcedureColumns is not used; instead an AQT query is used to obtain the parameter info. To specify this, you need to edit your sybasee.cfg (or sybasee1103.cfg) file to have a line with ‘aqtprocparms (note the single quote at the start) in the file.

If you use aqtprocparms, AQT cannot determine the parameter type so it will default to IN. You will need to change this manually to the correct type.

Transaction mode issues

MS Access doesn't fully support transaction mode. This will cause problems in the following areas:

  • if you use Transaction mode

  • if you set Safe Update mode on

  • if you deselect Options > Technical Parameters > Auto commit

  • in the Data Loader if you change Commit options to anything other than Every row