---
title: Common Vet List Questions
slug: help/en-us/dairycomp/common-vet-list-questions
docTags: 
createdAt: 2026-01-26T11:43:20.696Z
---

Expand the topics below when working with vet lists for help with some common questions:  &#x20;

:::ExpandableHeading
## Why are too many animals on my vet list?

There are several possible reasons for having too many animals on your vet list:

- The FOR criteria in your vet list command is faulty.
- The criteria for your vet codes is wrong.
- The reproductive status of the animals is out of date.

Start by reviewing a few specific animals from the list one at a time to determine if the FOR criteria is wrong in the vet list command or if the animal's reproductive status is incorrect.

If the animal's status is correct but it should NOT be on the list, clear the [vet codes](docId\:X19x6Ohp4PHKDVs1MuWc0) by running the following command (to reset all the vet codes to new parameters as defined in the system's vet list table):

<font color="#6b7280">**=0**  **&gt;1** **&lt;&gt;6 &lt;enter&gt;**</font>

Once you've entered the above command, generate the vet list again.

If the steps above fail to solve the problem, try running the CHKFILE command with the **Repair access table** option and then rerun the vet list.
:::

:::ExpandableHeading
## Why aren't more animals on my vet list?

If there are not enough animals on the vet list, the cause(s) may be the same as those for having too many animals on the list (above). Another possibility is that the cowfile is damaged. In this case, contact [VAS Support](http://dc-help.vas.com/default.htm#cshid=2000).
:::

:::ExpandableHeading{customAnchorSlug="EntryOrder"}
## Why is the entry routine for animals in the wrong order?

Normally, vet entry information is entered for animals in the same order that the animals appear on the vet list. If the vet entry order is out of synch, consider the following:

- FOR and BY statements must be the same in the `VENTER` command as they are in the VETLIST command.
  If they are not, make the necessary changes to the commands to ensure that they match.
- Vet exam results should be entered soon after the vet list is generated.
  Delaying the entry of exam results can cause animals to be brought up in a different order. Re-running the vet list can bring the process back close to the same order, but usually with some differences. The best precaution is to enter the results quickly following the next vet check.

For information about the exam results entry process, see [Enter Vet Exam Results](docId\:RENqJbQup3GFSy32GMc05).
:::

:::ExpandableHeading
## How do I keep certain animals off my vet list?

There are various reasons you might want certain animals kept off vet lists. For example, you might want to delay rechecking animals for pregnancy that have been checked very recently. See [Hold Animals from Vet Lists](docId\:gZ-Q1QY0Ngjj5H4EZXuyJ) for more information.
:::

:::ExpandableHeading
## How do I keep FRESH animals off my vet list?

Follow the steps below to prevent FRESH animals from being included in vet lists:

1. Disable the FRESH vet code.
   Vet codes can be enabled/disabled through the **ALTER** command. See [Vet Codes](docId\:X19x6Ohp4PHKDVs1MuWc0) to learn more.
2. Change the FRESH command to set fresh animals to OPEN when they calve.
   To do this, use the **ALTER\3** command to add **RC=3** to the end of the FRESH command.
3. In the command line, enter **RC=3 FOR** **RC=2**. This will set all of the currently FRESH animals to OPEN.

See [Hold Animals from Vet Lists](docId\:gZ-Q1QY0Ngjj5H4EZXuyJ) for more information.
:::

:::ExpandableHeading
## How do I create a separate vet list for heifers?

Many dairies prefer a separate vet list for heifers (i.e., animals with lactation=0). This can be done by creating a new command/menu abbreviation that creates a vet list just for heifers, as in:

<font color="#6b7280">**HVLIST=**  **VITEMS**   **&gt;0** **=0**  </font>

If you want to create an items grouping specifically for use in your heifers vet list command, you can do that as well. For example:

<font color="#EAB308">**HVITEMS=**</font>****<font color="#6b7280">      **EVT**  </font>

In this case, you would replace the VITEMS in your new command string with HVITEMS:

<font color="#6b7280">**HVLIST=**  </font>****<font color="#EAB308">**HVITEMS**</font> <font color="#6b7280">  **&gt;0** **=0**  </font>

See [Group Vet List Items](docId\:VZCVTWvCfxGxrsPmHUvDZ) for more information.

Finally, you'll want to create a new command for your vet entry routine, such as:

<font color="#EAB308">**HVENTER=**</font>VETENT FOR LACT=0 VC>0 BY PEN
:::

::::ExpandableHeading
## Why is my printed vet list not aligned?

It is recommended that you set your DairyComp printing font to Courier New or Lucida Console when printing vet lists to avoid any alignment problems when printing. See [Change Font in Printed Reports](docId\:WTYClhIrNVX1r-87xCeay) to learn how. For additional information about printing, see [Print Reports and Change Layout](docId\:kLJ0jTSOajW7SAAZHIncQ).

:::hint{type="info"}
**NOTE:&#x20;**&#x4D;ost vet lists are set up for compressed printing in order to supply more information (e.g., pen number, milk production, etc.).
:::
::::

:::ExpandableHeading{customAnchorSlug="adjust-hldat"}
## How do I adjust the HLDAT?

See [Adjust the Hold Date (HLDAT)HLDAT)](docId\:gZ-Q1QY0Ngjj5H4EZXuyJ) for instructions.
:::

::::ExpandableHeading{customAnchorSlug="DNBcows"}
## Why are DNB cows on my vet list?

When a DNB cow shows up on a vet list for a PREG check, the cow was likely not declared OPEN after she was bred. As a result, DairyComp adds the cow to the vet list to confirm if the cow is OPEN or PREG.

:::hint{type="info"}
**NOTE:&#x20;**&#x53;ometimes a DNB event is added for a cow and then removed later to make her eligible again for breeding.
:::

See [Hold Animals from Vet Lists](docId\:gZ-Q1QY0Ngjj5H4EZXuyJ) for more information.
::::

:::ExpandableHeading{customAnchorSlug="alter-vetlist"}
## How do I change or alter my vet list?

To change or alter your VETLIST or vet codes, please contact [VAS Support](http://dc-help.vas.com/default.htm#cshid=2000) because some vet codes might be tied to ovsynch.

You can also adjust the pens or vet codes you are checking by using a FOR statement for a VETLIST. See [VLCON](docId\:RENqJbQup3GFSy32GMc05) to learn more about a custom item that can be used to define additional parameters in a command.
:::

::::ExpandableHeading{customAnchorSlug="seeresults-vetcheck"}
## How do I see my results from a vet check?

In the command line, enter a SHOW command to review results from a vet check. DairyComp uses a vet check combination event to generate the report.

:::hint{type="info"}
**NOTE:&#x20;**&#x49;f your dairy does not already have a vet check combination event, see [Create a Combo Event](docId:8-YOPeCfYeksw0DKFyiSm).
:::

The following command generates a report that shows you the results of your vet check with **VREM** remarks:

<font color="#6b7280">         **=%WHAT\_DATE\_CHECKED**</font>

:::hint{type="info"}
**NOTE:&#x20;**&#x49;f your dairy does not already have a **VREM** item definition, see

[How do I create a list based on a vet remark?](docId\:DbF7aR2sBnGSYEy3oHCju) for more information. When th`%WHAT_DATE_CHECKED`switch is entered in the command line, DairyComp opens the **Enter Date&#x20;**&#x77;indow and allows you to select a specific date for the report.

::Image[]{src="https://api.archbee.com/api/optimize/3h8pSJcGUXEi4HGCCYPTA/aUUc72vUj5da9HhdCNXN3_enter-date.png" size="58" width="1169" height="515" darkWidth="1169" darkHeight="515" position="flex-start" showCaption="false"}
:::

You can also edit the events to include in a combo event for a vet list if necessary. See [Edit a Combo Event for a Vet List](docId\:wXor8sy-Kl5yMfGDCGcKJ) for instructions.
::::

:::::ExpandableHeading{customAnchorSlug="vrem-vetlist"}
## How do I create a list based on a vet remark?

Follow the steps below to create a vet list based on a vet remark:

1. Confirm that DairyComp includes a VREM item definition by entering **ALTER\2&#x20;**&#x49;n the command line and locating the **VREM** item definition in the ALTER2 : Item Definitions window.

   ::Image[]{src="https://api.archbee.com/api/optimize/3h8pSJcGUXEi4HGCCYPTA/nPVXRt5VvuANp8otH-Fth_itemdefinitions-vrem.png" size="32" width="1109" height="723" position="flex-start" darkWidth="1109" darkHeight="723" showCaption="false"}

   ::::ExpandableHeading{isOpen="true"}
   ## If your dairy does not already have a VREM item definition, click here for instructions on adding one.

   1. In the command line, enter **ALTER\2** to view your item definitions.
      The ALTER2 : Item Definitions window opens, showing all item definitions configured for DairyComp.

      ::Image[]{src="https://api.archbee.com/api/optimize/3h8pSJcGUXEi4HGCCYPTA/kSm6QPHbg_DTt3WSBckdB_itemdefinitions.png" size="32" width="1115" height="638" position="flex-start" darkWidth="1115" darkHeight="638" showCaption="false"}
   2. Click **Add \[Ins]** and enter VREM in the **Item Name** field in the pop-up window.

      ::Image[]{src="https://api.archbee.com/api/optimize/3h8pSJcGUXEi4HGCCYPTA/OokpDbVVBzTcAz1nPBh0k_itemdefinition-add.png" size="32" width="621" height="405" position="flex-start" darkWidth="621" darkHeight="405" showCaption="false"}
   3. Click the **Next** button and select **73 - Remark of event** in the **Item Type** drop-down list.

      ::Image[]{src="https://api.archbee.com/api/optimize/3h8pSJcGUXEi4HGCCYPTA/nIQyETF_MVMZqNklHS8o9_itemdefinitions-vrem-remark.png" size="32" width="667" height="405" position="flex-start" darkWidth="667" darkHeight="405" showCaption="false"}
   4. Click the **Next** button and select the vet check combination event that you want to associate with the **VREM** item definition.

      ::Image[]{src="https://api.archbee.com/api/optimize/3h8pSJcGUXEi4HGCCYPTA/KARkrNJJRD5kHOFhD4TXI_itemdefinitions-vrem-event.png" size="32" width="702" height="285" position="flex-start" darkWidth="702" darkHeight="285" showCaption="false"}

      :::hint{type="info"}
      **NOTE:&#x20;**&#x49;f your dairy does not already have a vet check combination event, see [Create a Combo Event](docId:8-YOPeCfYeksw0DKFyiSm).
      :::
   5. Click **OK** to save the new item definition and event association.
   ::::
2. In the command line, enter **ALTER\2** to view your item definitions.
   The Item Definitions window opens, showing all items configured for DairyComp.

   ::Image[]{src="https://api.archbee.com/api/optimize/3h8pSJcGUXEi4HGCCYPTA/kSm6QPHbg_DTt3WSBckdB_itemdefinitions.png" size="32" width="1115" height="638" position="flex-start" darkWidth="1115" darkHeight="638" showCaption="false"}
3. Verify that a **VREM** item definition already exists for your dairy.
   The example below shows an existing **VREM** event definition.

   ::Image[]{src="https://api.archbee.com/api/optimize/3h8pSJcGUXEi4HGCCYPTA/nPVXRt5VvuANp8otH-Fth_itemdefinitions-vrem.png" size="32" width="1109" height="723" position="flex-start" darkWidth="1109" darkHeight="723" showCaption="false"}
4. [Run a report in the command line](docId:3jlKSrsMd3IIMosqDWeMC) that includes **VREM** remarks.

   :::hint{type="info"}
   **NOTE:&#x20;**&#x41;ny event that has a **VREM** remark is included in the vet list.
   :::

:::Paragraph{indent="1"}
For example, the command below generates a report that includes **VREM** remarks: <font color="#6b7280">     **&gt;0**</font>
Running this command generates a list of animals that have events associated with the **VREM** remark for a vet date greater than 0.
:::

::Image[]{src="https://api.archbee.com/api/optimize/3h8pSJcGUXEi4HGCCYPTA/6WCQ0uETrQEQqaJSSQLFt_showvdatvremreport.png" size="32" width="523" height="414" position="flex-start" darkWidth="523" darkHeight="414" showCaption="false" indent="2"}
:::::

