Frequent Asked Questions

Please be so kind and verify the presence of license file! You license file - after the registration process - has been sent to the email address specified by you. You must save the vqt.lic file sent as an attachment in the same directory with vqt executable.

If you are registered customer or in the meantime of trial period - for the same computer, yes.

Your installation is too old. Please check for a newer version on the Internet. You must delete vqt.lic before making a new registration.

Probably your license has been expired. If you are in valid trial period, please verify your computers system time.

If you are registered customer, please contact the technical support team.

There can be multiple problems. The current version can not been handle password-protected proxy servers. Another source of problems can be an erroneous operating system functionality. Please patch your OS.

The solution is an indirect activating: please make "manual registration" using the dedicated web-page instead of email registration, because this is quickly. The email registration is recommended only if you do not have Internet connection on the target machine.

The application has been launched in User mode. Some functionalities are enabled only in Designer mode. To enter Designer mode you can right-click on a package in Windows Explorer and select the Edit command instead of double-click activating Open command or you can prepare a shortcut to vqt executable having the /D command line parameter (according to the accepted command line syntax: <path>\vqt [<option>] <package>[.vqt]).

Starting vqt executable with no parameters in command line it will search the Tutorial package and it will open in designer mode.

The application is not died. Please observe the replacement of Execute toolbar button with Step and Stop buttons in main toolbar. The presence of these buttons mean that the executing command is a multitask command and the flow of execution is interrupted; the decision to continue (Step) or interrupt (Stop) the execution is at the user level. Unless your decision the application can not been interrupted by closing the main window.

There is an invalid licence file present on target computer. To request a temporary licence before this you must delete the existing invalid or expired licence file. Note: please do not forget you are entitled only once to get a licence file.

Please check the following: [1] The path to service itself can not contain white spaces (it is a Windows restriction). [2] The account under the service runs must have access to the named ODBC drivers and directories. It is possible that the default Local System Account has not adequate rights, and you must create or nominate an another account. [3] You must have a valid license.

The Commit (as Recall too) after execution updates the databases and closes the connection. The data (in tabular or form view) remains displayed but not supports any kind of navigation.

Yes. After installation it starts in demo mode. To use it with full functionality you must activate it. The trial activating is free of charge. Please take a look on Visual Query Tool website, at Download & Activate | Activate VQT chapter.

To install the Visual Query Tool Package it is required a MS-Windows compatible system. The product was tested on MS-Windows 95\98, MS-Windows 2000, on NT and Windows/XP too.

Minimal problems were encountered on MS-Windows 96\98, as is the application is not able to use external icon resources. The most important speed factor is the used data engine behind the ODBC.

The virtual memory needs of application are about 20-25 Mb.

Yes. But VQT is not a really multitasking system. You can study the precedent result until a query run, or you can complete other jobs, but you cannot start another SQL processing. This can result in hanging of application.

Problems with Visual FoxPro ODBC driver. Works well, but on closing the connections the application can trigger unexpected errors. This can happen on exit or on new package running. It is recommended to quit the application after all DBF-related processing was completed.

Only the result of a select task is ready to display. You can not use the result of a statement (insert, update, create table, U) nor a PL/SQL procedure to present as a table, form or business graphic.

Naturally yes. Please contact NetWorks by email, to notify it about this hardware-change. Because the licensing is system-dependent, on problems you can achieve a temporary activating key for the new hardware (see chapter "Activate Product | HW-Change" for details) until official forms ends.

Yes. Please use the first toolbar button from left of result datapage. This is the Copy button. The graphics is copied into the clipboard, and after this it can be pasted in other documents as an image. Please notify, this is only an image, not a live object.

This works relatively reliable, but now this is under experience. The best way is to make save copies of well working packages. This version of Visual Query Tool does not support versioning.

The only reported problems are related to cancelled parameter page editing. Due to a program malfunction, on cancelling control editing window, some properties of current selected control are and some are not changed. This can interfere and it is possible to trigger an application crash. No possibilities to recover all control information regarding the lans-edited control.

The packages can be protected by designer to hide implementation details as command's structure, task's text code and control initialisation. On this way the unauthorised modification is disabled too.

On the other hand specifying an incomplete connection the user is forced do give at connection time - when first executes a command from a bindery - the lack parameter, for example the SQL engine's password.

The most tested database is Oracle 8.x. It is important to notify, that this driver supports unnamed PL/SQL procedures as well as DDL statements and DML queries. This is a very efficient way to implement data processing involving high complexity processes. Evidently it is a mistake to display the result of a PL/SQL procedure.

In the case of a wrong SQL expression it is possible to get from Oracle only an incomplete suggestion about the nature of raised error. Instead, in the case of an SQL procedure Oracle reports the exact position (i.e. row, column) and the error that triggered the error. To debug a statement, the easier way is to prefix the text with begin, and to suffix with ;end;. In this manner the statement transforms in a PL/SQL procedure. After localization and correction of error, the only reported error in the case of a select will be about the missed into clause. In this moment the prefixing begin and suffixing ;end; can be removed. This technique can be very useful in debugging of complicated select statements.

No great problems. There are a limited set of available non-aggregate functions. See for details the MS-Jet documentation.

This ODBC driver does not support select in select. Robust, good response time. See for details the Visual FoxPro documentation.

Undocumented function: iif()

Yes, well.

Yes, well.