What is VQLog? FAQ related to importation FAQ related to rig control (CAT)
Download awards (ADF) Download CAT definitions (CDF)    Download TABLAS file
Frequently Asked Questions

Versión Española         Add this site to your Favourites             Twitter             Facebook      Telegram

I don't get any DX-Spots into VQLog, although I have DXTelnet running properly. What's wrong?

Communication between DXTelnet and VQLog is achieved via DDE which can be somehow cumbersome because of the 16-bit nature of DXTelnet and the required configuration parameters. Have a look to a detailed explanation of how to setup  the connection.

Please notice that version 3.1 build 203 of VQLog implements the direct connection to DX-Cluster, so the use of DX-Telnet or Livemuf is no longer required to get the spots.

I would like to have VQLog texts in my own language. Is there some kind of multilingual support ? Could I make the translation on my own?

VQLog supports the use of foreign language plug-in files. You can check which languages are available or you can make yourself the translation.

Is it possible to maintain different log files, for example for contest operation and private operation? I make contests with a different callsign, and I would like to have those QSO in the program for statistical purposes. But I do not want them mixed up with my private QSO. Is that possible?

Yes. You can create as many log files as you want but bear in mind that they will be completely independent. Most users will prefer to use a single file so that they can have an overview of all their activity independently of their location or callsign used.

I have two different callsigns.  How is VQLog supporting this?

You have two possibilities.

  1. Use a single log and register the callsign you have used in the field "My callsign" for each QSO.

  2. Run two separate log files.

If you want to have completely separate award tracking for each callsign I suggest you the second option, but if you prefer to have an overall view of all your activity, independently of the callsigns used then you should go for the first option. (I personally use that one)

I have been using VQLog in two different computers, one at home at another at my portable QTH. Each computer has the different QSO made from each QTH, but now I want to combine (merge) both logs into a single file for using it at home. How can I do this?

The way to combine two files is to export one of them to ADIF format and them import that ADIF file into the other computer.

In this case you should export the log to ADIF format from the computer in your portable QTH (using the provided function), then move that ADIF file to your home computer and finally import it there using the corresponding function.

If you notice that as a result of the importation you have duplicate QSO you can always use the function "File - Maintenance - Purge duplicate records".

Important: The recommended procedure to keep VQLog installed in two computers is described below.

I have VQLog installed on my desktop computer at home, and also on a laptop computer I use on weekends from my country QTH.  How can I move the log from one computer to the other so that I always have the latest QSOs?.

First of all you MUST be using exactly the same version of VQLog on both computers.  If you do so then you simply have to move the LOG.MDB (or the log file you could have created) file from one computer to the other (using an USB drive, CD, LAN or pc-to-pc communication)

In your case you should move that file from your desktop computer to the laptop when leaving home for the weekend and then move it back to the desktop computer when coming back home.

Notice that if you also wish to move the configuration of the program you have to move the file CONFIG.MDB (or the configuration file you could have created) additionally

Important: If you copy the files in a CD, they are very likely to be mark as "Read only". After putting them back in the hard disk, with Windows Explorer you must edit the properties of the file(s) and make sure they DON'T have the "Read only" mark set.

I have two PCs at home and I want to use VQLog in both of them but sharing the same log and configuration files. How to do it?

You must have both PCs connected to a LAN (network) and then you can use the same LOG.MDB / CONFIG.MDB (or whatever log/configuration file you could have created) in both computers. This is one example of how it could be done:

Let's suppose you have currently VQLog installed in the PC#1 and you are using the LOG.MDB file as your log file and CONFIG.MDB as your configuration file (these are the default files), both in the drive C: 

  1. Install VQLog in the other PC#2
  2. In PC#1 you should share your drive C:
  3. In PC#2 connect to the drive C: of PC#1 and name it as the network drive V: (for instance)
  4. Run VQLog in PC#2 and use the function "File - Open - Log file" to choose the file LOG.MDB in the corresponding folder of drive V:
  5. Use "File - Open - Configuration file" in the same way to select the CONFIG.MDB file from the drive V: if you also want to use the same configuration profile in both computers.

At this point both computers will be using the same log and configuration files.

You MUST be using exactly the same version of VQLog on both computers

Can I use a network drive (Onedrive, Google drive, etc) for sharing the log between two computers in different QTH?

Onedrive, Google drive and other online file synchronization  tools lock files from time to time, while synchronizing them, and VQLog requires to have full control of them.  You can try it, but at your own risk. If you get program errors or the files get corrupted I won't be able to help you, so I strongly discourage it.

I have two radio QTH, one in the city and another by the countryside.  What I do is simply copy the full log file and that's it.  You can use Google drive, etc. (or USB drive or any other way) to copy the log file in order to move it from one QTH to the other, but when you are in the second QTH you have to copy it from there to VQLog's folder.

You MUST be using exactly the same version of VQLog on both computers

After resizing the main window I have lost some of the fields. Is this behaviour normal and what can I do?

The controls (texts, fields, etc) in the main window are automatically reallocated to fit the size of the window. This is true for window sizes of at least 640x480, that is the smallest size that can hold all the controls. If you make a smaller window some of the controls will no appear on it. You can enlarge the window till you see again all the controls or maximize it.

How can I be informed of the new versions and updates?

If you are a registered user you can be notified by E-Mail. You just have to join The VQLog's Mailing List or follow VQLog on Twitter or Facebook

None of the predefined formats (sizes) of labels matches the labels I use. Can I use other formats?

Yes, any type of label can be defined by using the "User defined labels" and configuring a few parameters of your labels (see next).

I have configured the "User defined labels", but it doesn't print as I would like (or it gives me some error message when printing)

This is always due to entering wrong parameters in the configuration of the user defined labels. Please double check them and make sure they are OK. Here you have a graphical explanation of the meaning of each of them.

1.- Top sheet margin

2.- Vertical gap between labels

3.- Left sheet margin

4.- Horizontal gap between labels

5.- Number of labels (Horizontal)

6.- Number of labels (Vertical)

7.- Width of labels

8.- Height of labels


How can I print my QSL-labels using Avery #8160 (or #5160) address labels?

You have to configure them as "User defined labels" with the following parameters

Why the sample of labels doesn't show the whole label? The text of the label doesn't fit the sample.

The size of the area of the sample depends on the type of label you have selected, while the text shown in it depends on the format (1 or 2) and the selected fonts. Although, theoretically you can adjust both formats to any type of label (adjusting the size of the fonts), normally you will use Format-1 for labels of 105x25.4 (or any other "long" label) and Format-2 for labels of 70x35 (or any other "less long" label). The best is to "play-around" with the formats, types of labels and fonts till getting the label you like, but bear in mind that what is shown in the sample is what will be printed (WYSIWYG) and that if the texts don't fit the sample they won't fit the label when being printed.

Can I can print QSL labels with a label printer?

Label printers are very special devices, not like a standard printer.  VQLog has been confirmed to work with the Brother QL-710W, it might work with other label printers, but it is not sure.

In order to configure the printing of QSL labels in the QL-710W follow the next steps:

  1. Use "File - Printer and paper selection" to select the QL-710W printer. In this case the "Paper size" selection is not taken into account.
  2. Go to "Configuration - QSL labels printout" and define and select "User defined" labels.

  3. If the labels are printed with a wrong orientation, then go to "Configuration - QSL printout" and change the "Printout orientation"

If I print QSL labels on the DIN A4 3x8 sheet with the QRG in "MHz.kHz" format, the RST field in the right label column is cut in the middle. Abt 5mm too broad...and if I print QSL labels with format 1 on the DIN A4 2x11 sheet, also with the QRG in MHz.kHz format, the 2Way field is cut in the middle. How can I print the MHz.kHz on the QSL label?

You need to change the font or font-size (reducing it) of the "QSO-data", so that the label holds all the fields (Even with the MHz.kHz format).
Another possibility is to use a wider label. In this case you will have to define your own type of label (using "Configuration" / "QSL labels printout" and selecting the "User defined" type). Here you can enter the parameters (number of labels per sheet, size of the labels, margins, etc.) at will.

I want to print directly on the QSL cards and VQLog's functions doesn't make the job in my case because I want to design the printout of the QSO data on the QSL card. I also don't like to print QSL labels. How can I print directly my QSL cards ?

You need an additional program that takes care of handling the printing and that is fed with data from VQLog.

  1. Print QSLs normally in VQLog. This actually only stores the QSL information in a "QSL-Queue".
  2. Export the QSL-Queue to an ADIF file, by selecting the provided function in the "Print - QSL queue" menu.
  3. Use the generated ADIF file to feed a QSL printing program, such as Adif2QSL, BV-Label  or HamLabel

When an SWL sends me a QSL, what must I do in order to confirm his report?

You must enter it as QSO, but with the following differences:

  1. You must leave the report-sent field blank (empty)
  2. You must fill the report-received field with the report from the SWL
  3. You must tick the SWL box

In this way the program won't consider it as QSO (for award counting, etc) and the QSL will be printed properly.

When I listen to a beacon, etc. and I want to send a QSL reporting its reception, what must I do in order to print it with the program?

You must enter it as QSO, but with the following differences:

  1. You must leave the report-received field blank (empty)
  2. You must fill the report-sent field with the signal report of the beacon, etc.
  3. You must tick the SWL box

In this way the program won't consider it as QSO (for award counting, etc) and the QSL will be printed properly.

How can I generate individual QSL cards in PDF format for sending by email?

NOTICE: The following is only valid for VQLog 3.1-build 733 and later versions.

First of all you must have a virtual PDF printer defined in your computer. Newer versions of Windows have one by default but it doesn't allow programs to set the paper size, so as a result you will get a PDF file with the size of an A4 sheet and the QSL card will only take up a part of it, what is possibly not what you want.

For this purpose I strongly encourage to use Win2PDF that allows to set smaller paper sizes, closer to the size of a normal QSL card. Unfortunately this software is not free but there is a trial version you can try. 

It could be that there are other virtual PDF printer programs that also allow to set small paper sizes, but I don't know of any apart from Win2PDF

Go to "File - Printer and paper selection" and select the Win2PDF PDF printer.

Go to "Configuration - QSL printout" and configure the QSL parameters like this:

You can use the "Print sample" button to check how the PDF QSL cards will look like.

I would like to use the program for contest-logging but there are no fields to register the serial number sent/received. I also would like to print the contest logs. Do I have a chance to do this?

No. VQLog is not intended to be a contest-logging program. There are many good programs for contests (Tac-Loc, TCC, CT, etc) and my point of view is that you should use them for registering the contacts / printing the logs.....Later, you can import the QSOs to VQLog, that would become a general log with ALL your QSOs (Both contest and non-contest)

I used VQLog in the ARRL DX contest last weekend and it coped really well as a contest logger as well!!.
Is it somehow possible to export data as a Cabrillo format from VQLog?

VQLog is not intended to be a contest logger, but a logbook program. Anyway you could try exporting the contest QSOs in ADIF format and then convert that ADIF file to Cabrillo using the LogConv utility program

When I upload and ADIF file to LoTW it rejects some of the QSOs made in digital modes. Why?

LoTW only accepts a subset of all digital modes available nowadays. In order to be able to upload your JT44, JT65, FSK441, BPSK, etc. digital contacts you will have to use the LoTW mapping features in the TQSL program, forcing each of these modes to be converted to a mode that LoTW considers "legal".

Use the custom ADIF mode mapping function in the LOTW TQSL program. To set the mapping mode in TQSL, first start the TQSL program.  Next click on File --> Preferences --> ADIF Modes tab. Now click on Add and enter BPSK (for instance), and then select the "legal" mode PSK31 (for instance) from the listing shown in the included table.

I like the program very much and I would like to use it from now on, but I already have thousands of QSO's registered with another logbook program. Is there any way to copy automatically these contacts to VQLog.

Please visit the importation FAQs page

In the DX-Spots window, a "?" sign is shown in the LoTW column.  How can enable the identification of stations available in LoTW?

This happens because for whatever reason the LoTW2.mdb file is not in VQLog's folder (same folder than VQLog20.exe program). Use the menu "Options - Update LoTW2.mdb" of the DX-Spots window or the menu "File - Maitenance - Update LoTW2.mdb" of the QSO input window to download it automatically from Internet.

I have successfully imported several different files  but then I have noticed that the records were not sorted by date/time, but in the order I have made the importations. How can I have my records sorted by date / time?

The function "File - Maintenance - Recompute record numbers" sorts the records by date/time and assigns them the corresponding QSO number.

Is it possible to create a report where you have a full list of "waiting for an answer to a qsl card" ?

Of course. Just use the "Summaries - Summary of QSOs" function and then select the "Pending of confirmation" radio-button. (Rembember to enter the right criteria of the summary - "From date", "to date", etc....)

When I run a summary the program shows a message indicating that there are no records matching the search pattern.  Why ?

There are two usual situations which can cause this message to appear:

  1. You have selected too restrictive parameters in the summary window. Try selecting less restrictive parameters (Don't limit by distance, leave the own locator blank (from all locators), etc.). I suggest you try first with the least restrictive parameters by clicking on the "All QSOs" button.

  2. You have logged the QSO with wrong frequencies. Frequencies must be entered as MHz-dot-KHz (for instance 28.550, 144.300...) If you have entered them without the dot (28550, 144300...) that QSOs have not been assigned to the corresponding bands (10m, 2m....) and thus are not taken into account.

I had a computer crash and lost all programs, including VQLog. Now the computer is running again but, what must I do to get VQLog running ?

You have to follow this procedure.

  1. Install the complete version into a new folder with the SETUP program (if you don't have it you can download it from http://download.vqlog.com)
  2. Check that you can run the program without problems (obviously the log will be empty)
  3. Close the program.
  4. Restore the files from your backup copy (**1)
  5. Run VQLog again and your QSOs and configuration data should be there.

(**1) Files are backed-up to the specified folder/disk into a sub-folder named with the date you made the back-up ("26Sep2002" for instance). There you will have several files, depending on your settings:

The only thing you have to do is copy these files (from the most recent back-up) to the folder where you have VQLog installed in your hard-disk (by default it usually installs into "C:\VQLog" or "C:\Program files\VQLog 2......"), replacing the existing files.

Important: If you had the backup files in a CD, they are very likely to be marked as "Read only". With Windows Explorer you must edit the properties of the three files and make sure they DON'T have the "Read only" mark set.

When you re-start VQLog it will use the restored files.

I was using an older version of VQLog and now I need to reinstall it because of a computer crash (or because I bought a new computer). How should I proceed?

If your two-year update license is still valid you can install the current version. Look at the detailed procedures for restoring VQLog after a computer crash or how to move VQLog to a new computer.

If your two-year update period has expired then you have two options:

When I run the setup program I get a message error (it could be something like "Unexpected error",  “Cannot find the source file C:\DOC...\WZSEn.TMP\"   or other texts) and the installation finishes. How should I proceed?

This is very possibly due to something in your computer preventing the setup program to copy VQLog's files to the hard disk. The most likely reasons are:

I got a new computer and I have a backup from my log on a ZIP / USB drive. How can I restore my backup in my VQLog?

Files are backed-up to the specified folder/disk into a sub-folder named with the date you made the back-up ("26Sep2002" for instance). There you will have several files, depending on your settings:

The only thing you have to do is copy these files (from the most recent back-up) to the folder where you have VQLog installed in your hard-disk (by default it usually installs into "C:\VQLog" or "C:\Program files\VQLog 2......"), replacing the existing files.

Important: If you had the backup files in a CD, they are very likely to be marked as "Read only". With Windows Explorer you must edit the properties of the three files and make sure they DON'T have the "Read only" mark set.

When you re-start VQLog. it will use the restored files.

I have got a new computer. What must I do in order to get VQLog running on the new computer?

 You must install the complete version into a new folder of the new computer with the SETUP program (if you don't have it you can download it at http://download.vqlog.com)

  1. Check that you can start the program from the new folder without problems (obviusly the log will be empty)
  2. Close the program.
  3. Copy ONLY the VQLog.key, LOG.MDB, CONFIG.MDB and other Log or Configuration files you could have created, from the old computer to the folder you have  just installed VQLog. (replacing the existing files)
  4. If you had used the Addressbook then also copy back the DIRECC.MDB file
  5. Run the program again. Your old configuration and Log should appear now.
The way you copy the files from one computer to another depends on the configuration of you computers. Some possibilities are:
    - CD Rom
    - Network
    - USB drive
    - Etc..
Important: If you use a CD, make sure that files are not marked as "Read only" after copying them to the new computer. With Windows Explorer you must edit the properties of the copied files and make sure they DON'T have the "Read only" mark set.

My data in the VHF database is not accurate or it's not listed. How can I update it and made it available to anyone?

You just have to go to http://www.mmmonvhf.de/ and fill the update form.

I have downloaded the update patch but when I run it the computer tries to install a different program that has nothing to do with VQLog. What am I doing wrong?

Probably you have run the update patch directly from Internet, or you have placed it in your hard disk in a folder that was not empty.  Try again following strictly these steps.

  1. Create a new temporary folder (C:\TEMP\VQLOG for instance) and check that it's really empty.
  2. Download the update patch from http://update.vqlog.com and place it the temporary folder
  3. Run it and follow the update instructions.

After "recomputing record numbers" it seems I have lost some QSO, or at least the record number show in the QSO entry is lower that before.  Am I losing QSO when recomputing the record numbers ?

YOU ARE NOT losing QSO at all !!!!!!

It's simply that when you recompute record numbers the file is also renumbered, and the possible record numbers that were deleted are no longer in the database.... 

I'll try to explain it with an example.

Also, occasionally and under certain circumstances (importation of files, etc) it could happen that there are gaps in the numbers of records, and when recomputing record numbers these gaps are removed, showing then the real number of QSO.

So, don't worry at all...the real number of QSO is always OK after recomputing record numbers and all your QSO are there.

When entering QSO, after entering the callsign, the frequency or the mode it takes very long to change to the following field making the QSO input very slow. ?What's the reason of this? ?Is there a way to make it go faster?

When entering QSOs VQLog has to perform multiple verifications and accesses to several databases in order to show the information corresponding to that callsign, band and mode. In some old computers this overload can lead the program to take several seconds to pick up all necessary information, but it can be improved a lot by configuring the system properly:

For our licensing purposes (UK, etc.) I should register the callsigns I have "called", even if the QSO with that station is not achieved. How can I enter the callsign so that the program doesn't count that record for awards, etc.?

You can achieve that by ticking the SWL box. Those records having the SWL mark set doesn't count for awards, etc.

I have worked a station that I don't want to be counted for any DXCC country (and neither for any other award), how do I do it? For example if I find out later that I have worked a pirate station, how do I delete it from DXCC & award records but still retain it in my log?

There are two ways to do it. One is marking that QSO as SWL by ticking the SWL box and the other is setting the QSL complete indicator to "NO". In both cases it won't be taken into account for DXCC and other awards. 

How can I enter QSO made via EchoLink, eQSO or other Internet assisted contacts into the logbook and avoid them counting for awards, etc.?

Strictly speaking, those QSO are not Amateur Radio contacts because they use a non radio relay (Internet) and thus they should be logged in a separate logbook file. Doing it in this way you will avoid mixing them with your real Amateur Radio QSO and also you will have a complete separate award counting. Use function "File - New - Logbook file" to create a separate logbook for your Internet assisted contacts.

The other possibility is to log them in the same logbook file but ticking the SWL box, so that they don't count for awards.  However I strongly suggest you use the first option.

I am interested in tracking the members of 10-10 group I have worked. Is that possible ?
I am interested in tracking the US counties I have worked for the USA-County award. Is that possible ?

You have to add a new award using the function "Configuration - Awards" and selecting the corresponding ADF.  After you do so you will have a new field in the "Awards" tab for logging the 10-10 number/US county and a new function in the "Summaries - Awards" for making summaries of the the references worked, confirmed, etc.

I am interested in tracki

ng the references of a certain award that seems not to be supported by VQLog. What can I do?

You have to add a new award using the function "Configuration - Awards" and selecting the corresponding ADF (If available). If the ADF is not available then you can still define any award you want, but with limited functionalities.

After you do so you will have a new field in the "Awards" tab for logging the references of that award and a new function in the "Summaries - Awards" for making summaries of the the references worked, confirmed, etc.

I have lost my registration number and/or VQLOG.KEY file. How can I get them again? Can you E-Mail them to me again?

I'm sorry but I can't do that. You will have to register (buy) the program again in order to receive a new registration number and key file.

I like the ability to retrieve station data from callbook CDs, but I would prefer to be able to retrieve it directly from their internet sites (QRZ.COM, Buckmaster..). Is there some way to do it?

You can do it if you are an XML subscriber of QRZ.COM. "Free access" to callbook data directly from their internet pages is not going to be implement because of legal restrictions (the owners of those callbooks want you to buy the CD, subscribe to their services or at least watch the advertising in their WEB pages...).  There is "DLL Interface to Online callbook server" available at http://www.xmission.com/~toms/software/ that has been reported to work with VQLog but I fully discourage its use.  

IMPORTANT: If you decide to use that DLL remember you are doing it at your own risk.  VQLog.com is not responsible for it use and declines all liability for the possible illegal use of internet callbooks through that DLL.

If I use the function for browsing the logbook from begin (or from end) - I have strange dates in the line date/time ??? (example 05.03.2696 00:00) - If I go into the line with double click, the date and time in the "modify window" will be ok (for above exp. 29.07.1999 00:00)

This problem has to do with a strange behaviour of one of Microsoft's OCX controls...In order to work around it go the regional settings and change the "short date format" to "DD/MM/YY", instead of  "DD.MM.YY", and also the "Date separator" to "/" (slash), instead of "." (dot)

I have configured the program to show slashed zeros, but I get a strange character instead of the slashed zero. ¿Why?

This problem has to do with a non-English version of Windows and your regional settings.The ASCII value of the slashed zero character is not the same in all languages. You have to configure "English" as the language for non-Unicode programs.

When I try to open the map window the program freezes/become unresponsive and I have to restart it using the task manager.

The problem is that, at some time and without realizing, you had moved the map window outside of the Windows desktop, so in fact VQLog is not unresponsive but waiting for you to close the map window that is shown somewhere outside the visible area of the Windows desktop.

Search the words "window outside of screen" at Google and you will find several ways to move a window back to the visible area of the screen.

When I browse the logbook, some fields are shown too wide wasting space on the screen. Also some of the fields are not meaningful for me and I would like them not being shown. How can I achieve this?

You can change the width of the fields at will. As in other Windows applications you simply have to place the mouse pointer on the separation lines in the header row and drag it to the left or right (see picture). You can even completely hide a field by making the width of its column equal to zero. If at a later time you would like to restore the default column width, right-click anywhere in the "browse" window and select the option "Restore default column width"

Can I use VQLog in my MAC computer?

VQLog is only available for Windows operating systems, but it can be run in MAC computers using "Virtual PC for MAC" or "Oracle VirtualBox"

Can I use VQLog in Linux?

VQLog is only available for Windows operating systems, but it has been reported to run successfully in Linux computers using "VMware" and "VirtualBox".

It is also known to be working using Wine 0.9.6 on Linux Mint 4.0 (Ref. OZ1PIF). (watch image).

I am using Windows 98 and I have the time zone set to "GMT time (Greenwich, Dublin, Edimburg...)", but the time assumed by VQLog is one hour less than the PC time. What's the problem?

This seems to be related to a problem of Windows 98 reporting the time to applications. You can fix it simply by setting the time zone to "(GMT) Casablanca, Monrovia)" in the Control Panel of Windows.

I run the registered program and everything seems to be fine, but I still can't use all features in the software. Some buttons is still marked out in gray, and can not use those functions. How should I do to get full working software?

If you run the registered program then you have all functionalities available. However your should bear in mind that some of the functions and buttons are only available when it's possible to click on them. For instance, the "Open DX spots window" option will be greyed till you have properly set up a connection with DX-Telnet or LiveMUF, using the corresponding option of the configuration menu. The "CAT" option will be only available if you have properly configured CAT. The "Turn antenna" option will be greyed if you haven't configured yet the connection with ARS-WIN, etc, etc.....

Also, the options "Show map", "Print QSL", etc. during the QSO input will only be available when a correct callsign has been entered, remaining grayed if no callsign has been typed in yet. 

My PC crashed and after restoring the VQLog files I get an error 'vqlog20.exe caused a page fault in module msjet35.dll', or some other errors. What can I do?

Copying back the files to the restored computer is not enough. Please follow these steps:

  1. Install the complete version into a new folder with the SETUP program (if you don't have it you can download it from http://download.vqlog.com)
  2. Check that you can start the program from the new folder without problems (obviusly the log will be empty)
  3. Close the program.
  4. Copy ONLY the LOG.MDB, CONFIG.MDB and other Log or Configuration files you could have created, from the back-up to the folder you have just installed VQLog. (replacing the existing files)
  5. If you had used the Address book then also copy back the DIRECC.MDB file
  6. Run the program again. Your old configuration and Log should appear now.

When adding a QSO and in some functions I get the message "Runtime error 5. Invalid argument or procedure call". What's the reason?

This problem could happen because of little memory available. Try closing all other applications in order to reduce memory usage or add more memory to your computer if you have little (less than 32 Mb)

After restoring the LOG.MDB file from my backup I get an "Error 3051...." message when starting VQLog.

This error arises because the LOG.MDB file (or another Log file you could have created) is marked as "read only".  Using Windows Explorer select the file and look at its "properties".   Then un-check the "Read only" box and the file will be ready for VQLog. (IMPORTANT, also check that all the other files in VQLog's folder don't have the "read only" mark set)

When I run a certain function I get a "Run-time error '94': Invalid use of null"

Simply run the function "File - Maintenance - Repair/compact the database" and the error should no longer appear. If it persists then report it to VQLog's support with all possible details about the problem.

I have been using VQLog for some time but now when I start it comes up an error like "Error: 1706. No valid source could be found for product DAO. The windows installer cannot continue" and/or complaining that the file DAO.MSI could not be found.

This is due to a corrupted installation of Office-2000, even if Office-2000 seems to work OK for you. DAO components are installed also by Office although they are not used unless you access a database from Word / Excel, what is possible but not very usual.

Some ways to fix the problem:

When I start the program it comes up an error "Run-time Error: 52. Bad file name or number".

This is a very rare error due some wrong settings in the user profile. In order to fix it you have to delete your user profile and let Windows create it again.

You can find instructions on how delete Windows user profiles here or search the text "How to delete Windows user profile" at Google.

When I try to install the program (or run the update patch) I get an error saying that CreateProcess returned an error code 0x000000C1H. What's wrong?

This error is very likely to be caused by a corrupted installation file or error in the drive (USB disk, etc.) you have placed the installation file. Make sure that your drive has no errors and try downloading again the setup file.

For more information on the possible causes of this error read Microsoft's knowledge base article Q216231

I have been using VQLog without problems for years but today when I have recomputed record numbers it came up with an error message "Not a valid bookmark", and afterwards when I run the program again it says that the file LOG.MDB is not a valid database. What can I do to recover my log data?

This error is due to a corrupted MDB database (the LOG.MDB file in this case). This is a very rare situation, but when it happens you will have to recover the file from the latest backup and repair it using Microsoft's tools before being able to use it again in VQLog. I propose you follow these steps:

  1. Restore the LOG.MDB file (or any other log file you could have created) from the most recent backup
  2. Try compacting and repairing the file according to Microsoft's instructions
  3. Run VQLog again and see if it works now.

Eventually, if you are a registered user and you don't manage to solve the problem on your own then contact VQLog's support and send the MDB file from your newest backup.

TIP: Run regularly the function "File - Maintenance - Repair/Compact the database" in order to prevent the corruption of the database.

When I try to change the font of the QSLs or QSL labels I get a message saying "There are no fonts installed...". I have lots of fonts in my computer, so what's the problem?

This message appears because in the configuration of QSLs / QSL labels you have a reference to a font that no longer is available in your system. This usually happens because of two reasons:

  1. You have deleted the file corresponding to the font referenced in the QSL configuration.
  2. You have moved the configuration file of VQLog to a new computer that doesn't have the file corresponding to the referenced font.

In order to solve the problem you must add the file of the missing font to your system. Go to the Control Panel of Windows and select the "Fonts" option.

When I try to browse the logbook or when opening the "Last QSOs" window I got some of the following errors:
  "Error 3170: Couldn't find Installable ISAM"
  "Error 713: Class not registered"
  "Error 3445: Can't open a database created with a previous version of your application"
  "Error 525: Error accessing data"
  "Error 335: Could not access system registry"
  "Error 13 - Type mismatch"
  "Error 3447: The Jet VBA file (VBAJet.dll for 16-bit versions, or VBAJet32.dll for 32-bit versions) failed to initialize when called"

    (texts can be in other languages or be slightly different) and the program exits. What's wrong?

This has do to with an incomplete or wrong installation of Microsoft's Data Access components. Please understand that it's not a bug of VQLog, but the result of a bad configuration of Windows. Anyway I can suggest you do the following:

When I run VQLog I get a message "Error 3228: Selected Collating Sequence Not Supported by Operating System" (text can be different or in other languages) and the program exits. What's wrong?

This has do to with an incomplete or wrong installation of Microsoft's Data Access components. Please understand that it's not a bug of VQLog, but the result of a bad configuration of Windows. Anyway I can suggest you do the following:

When starting the program I get an "Error 80010108, The object invoked has disconnected from its clients." (text can be different or in other languages) and the program exits. What's wrong?

You are possibly using a network printer or a printer connected to another networked PC. If that printer is not available (network or PC are down, for instance) when the program starts it could cause that error. Simply make sure that the network printer is available (and mapped) from the PC where you run VQLog and start the program again.

After upgrading to the new version I always get a "Run time error 383..." when I select any option in the summaries menu. What's wrong?

This is because you have upgraded the program the wrong way. You have installed the new version in a new folder and then copied there all MDB files from the old folder.

The right way to upgrade to the new version is to update VQLog in the same folder you had the older version. In this way everything goes fine and you don't have to do anything else.

Anyway, if for some reason you want to go the hard way and install the new version in a separate folder, you must bear in mind that you only can copy the log, configuration and address-book files (By default they are LOG.MDB, CONFIG.MDB and DIRECC.MDB). You must NEVER copy the TABLAS.MDB, WORK.MDB or ANY other file.

I have been using VQLog without problems till today, but now when I try to run the program I get an error (50003 or others) and the program does not start.  What can I do to ?

This problem is usually related to the installation of some other program that has made a "wild installation" replacing some of the Windows shared components used by VQLog. I suggest to follow this procedure step by step.

  1. With Windows explorer, MyComputer, etc. go to the folder where you have VQLog installed (By default it installs in "C:\Program Files\VQLog....." folder)
  2. There locate the files LOG.MDB, CONFIG.MDB and DIRECC.MDB and copy them to a temporary folder (C:\TEMP\VQLog for instance)
  3. Also copy any other Log and Configuration files you could have created.
  4. Go to Windows control panel and in the "Add/Remove programs" option look for "VQLog..." and uninstall it.
  5. Install a new copy of VQLog with the complete setup program into a different folder, (copying the files is NOT enough). If you don't have the setup program you can download it from http://download.vqlog.com
  6. After the installation finish, run VQLog from the new folder and see if it starts normally (note that it won't have QSOs yet...of course)
  7. If VQLog starts now
    • Close the program
    • Copy the files LOG.MDB, CONFIG.MDB, DIRECC.MDB, etc. you have saved in steps 2 and 3 to the folder where you have just installed the new copy of VQLog, replacing the existing ones, which are empty.
    • Check that those files don't have the "read only" property set. With Windows explorer look at the properties of those files and make sure the "Read only" box is not marked.
    • Run VQLog again. Your configuration and QSOs should appear now
  8. If VQLog still doesn't start
    • If you are a registered user, contact VQLog's support with all possible details about your problem.
    • If you are not a registered user then I should remind you that support is only available for registered users.

I'm using Windows Vista and when I try to see the program help I get a message saying that the format is not supported in Vista.  How can I read the program help?

Microsoft has done it again!  Windows Vista does not offer support for the classic .hlp files, that are common in most Windows applications, including VQLog. You should update to version 3.1 that supports the format of help files required by Vista.

If you don't want to update to version 3.1 then all I can say is:

If you want to access VQLog's help as in former versions of Windows you will have to replace the winhlp32.exe file of Vista with the "old" (but good) version from XP. Detailed information on how to do this (and other possible workarounds) is available at http://www.annoyances.org/exec/show/article07-500

If you want to simply look at the help file from outside the program you can already download the new help file adapted to Windows Vista. This file does not integrate with VQLog 3.0B however.

When installing the program I get the following error "C:\WINDOWS\ST6UNST.EXE C:\WINDOWS\  the file could not be installed"

This is a rare error that seems to be related to a missing or corrupted cabinet.dll file. (That should normally be located in C:\Windows\System32).  You have to restore the original cabinet.dll file. You can also download it

When installing or running the program on a 64bit version of Windows I get some of the following errors:
     "An error occurred while registering the file C:\Windows\System32\COMCTL32.OCX" (or COMDLG32.OCX or MSWINSCK.OCX or MSFLXGRD.OCX)"
    "Component MSWINSCK.OCX (or COMCTL32.OCX or COMDLG32.OCX or MSFLXGRD.OCX) or one of its dependencies is not correctly registered: a file is missing or invalid"

In modern 64bit versions of Windows those Microsoft OCX controls must be located in the C:\Windows\SysWOW64 folder, but it seems that in your system they are at the wrong place, for whatever reason, or they are not correctly registered.

  1. If the .OCX file is actually in the C:\Windows\System32 folder, move it to the C:\Windows\SysWOW64 folder.  If it is already in C:\Windows\SysWOW64 then continue with the next step.
  2. Start the Windows Command Console with elevated privileges (as administrator)

    If you need more information on running the command console with elevated privileges you can have a look at this article
  3. Once the command console is open, register the file running the command regsvr32 C:\Windows\SysWOW64\Comctl32.ocx (or regsvr32 C:\Windows\SysWOW64\Comdlg32.ocx or regsvr32 C:\Windows\SysWOW64\mswinsck.ocx or regsvr32 C:\Windows\SysWOW64\msflxgrd.ocx  depending on your particular case)

Some users have reported that the issue was also solved running the setup and/or the program itself as administrator

From time to time the message "That file doesn't look like a rig parameter file".

That message appears because you have the CAT interface to some rig enabled and the program for whatever reason is not capable of accessing the associated CDF (CAT definition file).  This problem only arises in Windows Vista and later and it's not due to VQLog, but to some restriction of the operating system that makes the CDF unavailable to VQLog.  Some suggestions that could help:

I get an "error 48 in loading DLL" message. What can I do?

This is not an error of VQLog, but an error of Windows that causes that VQLog can't run. Usually this error indicates system .dll files have been corrupted or have been overwritten with incompatible versions. If you are running Microsoft Office, try reinstalling it to clear error. If you do not have Microsoft Office, we recommend updating to the most recent version of Internet Explorer. If this does not work, download the latest Microsoft Jet Engine pack.

Some users have reported fixing the problem simply copying the DAO360.DLL file into VQLog's folder (the same folder that contains the VQLog20.exe program)

You also have some information about this error at http://support.legacyfamilytree.com/article/AA-00702/0/Error-48-Error-in-loading-DLL.html

Some users have reported this problem arising due to Norton Utilities changing something in Windows, and have recovered simply using the recovery function of Norton.

You can also try reinstalling VQLog.

In none of the above fixes the error then Google for "error 48 in loading DLL"

Error 8020 "Error reading Com device" with CAT communications.

That error seems to be related to Prolific USB/Serial chip discrepancies in some USB cables, an older driver may be required in lieu of the one supplied by Windows.

Prolific is the recommended driver for all cables.
For Windows Vista, 7, 8 y 10:
Download Driver (Alternative download site) Windows may try to update this driver in the future. If this occurs, turn off automatic updates.

For Windows XP:
If you are using Win XP, the Prolific driver will run with no issues. This driver for Win XP can be found at: Download (Alternative download site)

File WORK.MDB does not correspond to this version of the program ...

File WORK.MDB is used by the program as a temporary work file for generating summaries, etc. The version of this file must match exactly the version of the program, and if for whatever reason you have a wrong version of the work file an error message will be shown indicating that fact.

If you are getting that message you simply have to download the right version of the WORK.MDB file and place it in VQLog's folder.

Is there a way to export my confirmed contacts in LoTW and import that confirmation into VQLog so the awards show the correct status?

In LoTW use “Your QSOs-Download report” to get an ADIF file with the confirmed contacts.
In VQLog use “File-Update QSL indicators” and select that ADIF file to update the QSL-Received value.
Bear in mind that you will also have to configure VQLog to consider Electronic QSLs as valid, in “Configuration-Program options-Electr.QSL”

In recent versions of VQLog this process has been even more automated and you can use menu "File - Update QSL indicators - From LoTW" to update them. It can also be done from eQSL using "File - Update QSL indicators - From eQSL"

Language specific characters are not displayed when typed. Why?

It has been reported that in some non-English versions of Windows 10 (Croatian for instance) when you type some language specific characters they are not displayed in VQLog.  In order to fix this you have to select the correct language for non-Unicode programs in Windows configuration.

Go to the Regional settings in the Control Panel of Windows and in the Administrative tab change the regional settings / System locale for non-Unicode programs.  You have more information here.

I have several log files and configuration files. How to start the program with an specific log and configuration files?

You have to start VQLog passing the log file and/or the configuration file name as parameters. For instance, running "VQLog.exe /L=log2.mdb /C=config2.mdb" will start the program with the log file log2.mdb and the configuration file config2.mdb.

Eventually I need to log several QSO with the same station, at the same time, and in the same band and mode, but the the program shows a message saying that there is already a QSO logged. How can I do it?

That control is necessary in order to avoid duplicate QSO entered by mistake. However you can enter several QSO with the same station, at the same time, just varying a little the entered frequency. I mean, for instance, if the QSO is on 14.200.0 you can enter one QSO on 14.200.0, another on 14.200.1, another on 14.200.2, etc. This is only a difference of 100 Hz, so not really important, and it will make the trick.

After using the auto-logging feature from MSHV, WSJT-X, JTDX, etc. feature I notice that summaries are not working as expected, apparently missing some QSO that are in the log. Why?

There are two issues, but they are not a fault in VQLog. I explain it:

MHSV and WSJT don't provide information of the own-call and own-locator in its log, so when auto-logging from MSHV or WJST those fields get blank in VQLog.  You are possibly running the summaries filtering by your call and your locator and obviously VQLog don’t take into account the QSO taken from MSHV/WSJT because they don’t contain that information and so are not passing the filtering criteria you established. You can leave blank the “From locator” and “Own callsign” fields when running the summaries in order not to filter by that criteria and then those QSO from MSHV/WSJT will be taken into account. (Update: Version 3.1-514 of VQLog allows to automatically assume the callsign/locator configured in "Configuration - Station data" for those programs not providing this data)

Additionally and regarding auto-logging from WSJT, WSJT-X and JTDX, those programs don't provide the propagation mode in its log, so when those QSO are imported they get an empty propagation mode in VQLog, and of course VQLog has no way to make summaries of propagation if that field is empty.

You can confirm those points yourself by editing the original log files (mshvlog.edim for MSHV and wsjtx_log.adif for WSJT-X and JTDX) with any text file editor, such as notepad.

As you can understand VQLog can’t do anything if the programs from where the QSO are taken are not providing the required information. One thing that most users do, in case you have not done it yet, is to use the semi-automatic logging, instead of the fully automatic logging, so that QSO are first send to VQLog’s normal QSO input window and you can complement the missing information (propagation mode, own call, own locator, etc.) before the QSO is actually logged in VQLog. You can enable semi-automatic logging in “Configuration – Program options – Auto.log” and selecting “Send first to the QSO entry Window”.

Filtering the DX-Spots by frequency range

If you want to filter the received DX-Spots so that spots on certain frequencies are not taken into account (for instance if you do not want to get DX-Spots of digital modes frequencies) you have to set the filter at the source, this is at the DX-Cluster node to which you are connecting.  The way to set filters at the node depends on the type of software used at the node.

For instance if the node is using the DX-Spider software you have the instructions on how to set frequency range filters at http://www.dxcluster.org/main/filtering_en-6.html

For other DX-Cluster software’s the way to set filters could be different and you will have to check its documentation. 

After enabling rotor control using ARSVCOM I get an error message saying that ARSVCOM can't be run.  How can I fix it?

The new version of ARSVCOM V6.10.1 (could it happen with other versions) when it's run in Windows 10 has some compatibility issues.  Right click on the ARSVCOM.EXE file and select Properties. Then enable the compatibility mode with Windows 8 as shown in this image.

The program has been working fine but now it shows very often the error message "Wrong day/month received in function CDateInt" . What can I do?

It is due to a date format change in the users file provided by eQSL.

I have made the required changes and now you should update the eQSL2.mdb file. Use "File - Maintenance - Update eQSL2.mdb" o alternatively download the ZIP file from https://www.dxmaps.com/zip/eQSL2.zip, extract the file eQSL2.mdb and copy it to VQLog's folder in your hard disk (By default it is C:\VQLog but you could have installed it in another folder)

When uploading QSO to EQSL or Clublog I get and error "Wininet Error 120007......" . What does it mean and what can I do?

Wininet error 12007 means: ERROR_INTERNET_NAME_NOT_RESOLVED The server name could not be resolved.

You can see it at https://learn.microsoft.com/en-us/windows/win32/wininet/wininet-errors

It means that VQLog cannot communicate over Internet with EQSL/Clublog because Windows (Wininet) is reporting to VQLog that it can't find the eqsl.cc/clublog.org server.

I am afraid I can't help you much more, because as you can see it is not a problem in VQlog, but something in your system that prevents VQLog from communicating with eqsl.cc/clublog.org.   Try to remember if you made some upgrade, changed some configuration of Windows, Firewall, Antivirus, etc. o installed something the day the issue first happened.

FAQs related to importation  |  FAQs related to rig control (CAT) Generic FAQs  |

Share: Twitter   Facebook   Home page Site map Radio Sherlock search engine Terms of service  Privacy  Cookies