Reading the F2 Product Information Screen in QuickBooks Desktop
When a repair, condense, or downgrade quote needs your file size and list counts, one screen in QuickBooks Desktop holds every number.
Almost every scoping conversation about a repair, condense, or downgrade opens with the same questions. How big is the company file? How many customers, vendors, and transactions does it hold? Which version and edition is it running? One screen inside QuickBooks Desktop answers all of them at once. Our engineers ask for a screenshot of it first because it replaces guesswork with facts.
The numbers anyone scoping your file will ask for
Size drives most decisions. A file of a few hundred megabytes will drag in daily use, and condense and conversion work are both measured against it. Name counts matter because Pro and Premier cap the combined name lists at 14,500 entries. Target counts matter because a condense removes targets, not just transactions, so targets are the truer measure of the work. Version, edition, and release decide whether a downgrade is possible and in which direction.
How do you open the Product Information screen?
The screen is read-only. Nothing in this procedure touches your data, so no backup and no single-user mode are needed.
- Open the company file in QuickBooks Desktop, on the machine that hosts it or on your own workstation.
- Press F2. On laptops where F2 shares a key with a hardware function, hold Fn while pressing it.
- Leave the window open while you read it, or go straight to capturing it.
If you run several company files, repeat the steps in each one. Size and counts differ from file to file, and mixing them up is the mistake we see most often in inbound details.
Reading the screen from top to bottom
The top block names the product, edition, and year, for example QuickBooks Desktop Enterprise 24.0. The release number, an R followed by digits, sits in the same area. Note both down. Two files described as "the same QuickBooks" can still be on different releases.
Below it, the File Information block shows the company file size, the total transaction count, and the target count. The List Information block shows customers, vendors, employees, other names, the total name count, and items. Every one of those numbers belongs in the screenshot. That is why a single capture covers most of what a scoping conversation needs.
Capturing a screenshot that is actually readable
- Bring the Product Information window to the front and move anything that overlaps it.
- Press the Windows logo key + Shift + S, then drag the selection around the whole window, edge to edge. On older Windows builds, use the Snipping Tool, or press Alt+PrtScn and paste into Paint.
- Save the capture as a PNG. Give it a name that says which company it belongs to.
- Open the saved file and view it at full size. You should be able to read the file size and every count. Retake it if anything is blurred.
- If you would rather not share the license number shown near the top, cover it with the annotation tool before sending. The numbers an engineer needs sit lower in the window.
A phone photo of the monitor is the fallback to avoid. Glare and skew make counts hard to read, and the small digits are exactly the ones that matter.
Details to send with the screenshot
The screenshot supplies the numbers; a few lines of context complete it. State which service you are scoping. For a condense, add the date of your first transaction and the cutoff date you want, the two dates that shape a plan for condensing an oversized QuickBooks company file. For a downgrade, name the exact target version, since an Enterprise to Pro or Premier downgrade is planned against both endpoints.
Also say whether the file uses Advanced Inventory or multi-currency, and whether it is a non-US edition. Run Verify Data and Rebuild Data from the Utilities submenu under File beforehand, and report the exact outcome. If Rebuild fails, note the error text word for word.
The limits of the Product Information screen
The screen describes the file, not its health. A tidy set of counts says nothing about data damage; a file can pass the eye test and still fail Verify. That is why we pair the screenshot with a Verify result rather than treating F2 as a diagnosis. When Rebuild fails, the problem sits deeper than any condense or downgrade reaches, and the file needs repair work on the database itself.
The window also reports database fragments. A rising count means wasted space inside the file. A full backup and restore rewrites the database compactly, and the count should drop afterward.
How do you know you captured the right thing?
The saved image shows the whole window, title bar included. The version line, the file size, and every count are legible at full size. When our engineers open the backup and see the same size and counts, the capture did its job. The quote then rests on facts rather than guesses.