Reading the QuickBooks F2 Product Information Screen Before a Repair or Condense
Before a repair or condense, learn which version, size, list, transaction, and target counts on the QuickBooks F2 screen show a file nearing its limits.
Before we repair or condense any company file, we ask for one screen. The Product Information window reports the version, the size, and the counts that tell us whether a file is healthy, heavy, or near its limits. Reading it takes two minutes and decides the plan.
How do you open the Product Information window?
Open the company file and let the Home page finish loading. Then:
- Press F2. Ctrl+1 does the same on a Windows keyboard, and Cmd+1 works on a Mac.
- Read the top block for the product, version, and release, and the middle block for the size and usage counts.
- Capture the full window with a screenshot and keep it with your repair notes as the baseline.
- If the image leaves your business, cover the license number first.
Nothing on this screen changes your data, so you can open it at any time, even with other users logged in. If the file will not open at all, F2 at the No Company Open screen still reports the program version, though not the file counts.
Version and release come first
The product line names the edition and the year, and that decides what the file can do next. Upgrades run one way. Once a file opens in a newer year, the older program will not read it again without a conversion; see our service for converting a QuickBooks company file back to an earlier version. The release, a small R number beside the version, is the maintenance level of your install. An out-of-date release can carry defects that were fixed later and that look exactly like data damage. Update the program before you blame the file.
File size is a symptom, not a verdict
QuickBooks Desktop has no published size ceiling for its own editions. A large file can run briskly while a modest one is broken. Watch the trend instead. Steady growth that tracks your sales volume is normal aging. A sudden jump with no matching business reason usually means audit trail bloat, imported duplicates, or an overactive add-on.
Edition matters here. Pro and Premier files slow down at smaller sizes than Enterprise, which was built for heavier databases. Treat size as one clue among several, never as the verdict.
When do list counts signal trouble?
The list block counts customers, vendors, employees, and other names. Pro and Premier cap the combined total at 14,500 names, and the program refuses new names outright at the ceiling. Trouble starts earlier. Long lists slow list windows, name dropdowns, and any report filtered by name.
Merging duplicate names lowers the count. Making a name inactive does not, because the ceiling counts inactive names too. Files pressed against the ceiling usually need condensing an oversized QuickBooks Desktop company file, since names used in transactions cannot simply be deleted.
Targets measure the real load
Transaction counts mislead on their own because transactions differ in weight. A target is one line of one transaction, and the header counts as one more. An invoice carrying five item lines is six targets. That is why a file with 80,000 bulky transactions can strain more than one holding 120,000 lean ones.
The target count is also the number QuickBooks Online watches. The migration path from Desktop refuses to run once a file passes 350,000 targets. If a move online is on your roadmap, read this figure first; an oversized file needs preparing a Desktop file for QuickBooks Online import before anyone begins.
Prepare the file before any repair or condense
- Make a full backup from the File menu, and store the QBB file somewhere away from the working folder.
- Switch to single-user mode from the File menu. Repair, verify, and condense operations need exclusive access.
- Write down the baseline numbers: size, transactions, targets, total names, and fragments.
- Run Verify Data under the File menu's Utilities submenu and keep the result message.
How do you confirm the work succeeded?
Open the F2 window again once the work finishes and compare it against your baseline. A successful condense shows a smaller file size, fewer transactions, fewer targets, and a lower names count if list reduction was included. The DB File Fragments figure, bottom left, should sit in single digits. A high count usually falls after a full backup and restore.
Then check substance, not just scale. Run a balance sheet and a profit and loss across the condense cutoff and compare them with reports you saved beforehand. Counts down and balances unchanged is the result you want.
This screen cannot see damage
Be plain about the limit: the F2 window measures scale, not integrity. A file with modest counts can still fail Verify or throw a 6000 series error when it opens, and the screen gives no hint of the cause. When a file fails QuickBooks Verify or Rebuild, the counts stop mattering and the file itself needs the attention. Read the screen, record what it says, and treat it as the starting measurement rather than the diagnosis.