Creating a new Excel File based on a template in VBA

calendar_today Asked Feb 6, 2012
thumb_up 13 upvotes
history Updated April 14, 2026

Direct Answer

set wb = workbooks.add("x:mytemplate.xls") allows you to create a NEW doc and specify the file to be used as a template. This is a prose walkthrough, ranked #48th of 95 by community upvote score, from 2012.


The Problem (Q-score 3, ranked #48th of 95 in the VBA Core archive)

The scenario as originally posted in 2012

I am building an application in Excel which will enable a user to select from a list of existing excel based tools that have been built. They will select the specific tool and hit a “create new” button. Upon clicking this button, the user will be asked to name the file. After entering the name, a new workbook needs to be created and placed in that specific tool’s project folder. I am having trouble implementing this in code. I have been able to find examples of code implementing copying templates from the active workbook, but nothing for creating something that is in another excel file entirely.

I believe I need to make a copy of the workbook that the user needs to recreate and then change the name and place the file in the desired location.

I would post some code to show what I’ve done so far, but I haven’t really made progress.

Thanks,

Why this Range / Worksheet targeting trips people up

The question centers on reaching a specific cell, range, or workbook object. In VBA Core, this is the #1 source of failures after activation events: every property (.Value, .Formula, .Address) behaves differently depending on whether the parent Workbook is explicit or implicit.


The Verified Solution — solid answer (above median) (+13)

Verbal answer — walkthrough without a code block

Note: the verified answer is a prose walkthrough. If you need a runnable sample, check VBA Core entries ranked in the top 10 of the same archive.

set wb = workbooks.add("x:mytemplate.xls") allows you to create a NEW doc and specify the file to be used as a template.


When to Use It — vintage (14+ years old, pre-2013)

Ranked #48th in its category — specialized fit

This pattern sits in the 89% tail relative to the top answer. Reach for it when your scenario closely matches the question title; otherwise browse the VBA Core archive for a higher-consensus alternative.

What changed between 2012 and 2026

The answer is 14 years old. The VBA Core object model has been stable across Office 2013, 2016, 2019, 2021, 365, and 2024/2026 LTSC, so the pattern still compiles. Changes that might affect you: 64-bit API declarations (use PtrSafe), blocked macros in downloaded files (Mark-of-the-Web), and the shift toward Office Scripts for web-first workflows.

help
Frequently Asked Questions

Is this above-median answer still worth copying?
expand_more

Answer score +13 vs the VBA Core archive median ~4; this entry is solid. The score plus 3 supporting upvotes on the question itself (+3) means the asker and 12 subsequent voters all validated the approach.

The answer has no code block — how do I turn it into a snippet?
expand_more

Use the walkthrough above as a checklist, then open a top-10 VBA Core archive entry for a concrete starting template you can adapt.

This answer is 14 years old. Is it still relevant in 2026?
expand_more

Published 2012, which is 14 year(s) before today’s Office 2026 build. The VBA Core object model has had no breaking changes in that window. Three things to re-test: (1) blocked macros on downloaded files (Mark-of-the-Web), (2) 64-bit API declarations (PtrSafe, LongPtr), (3) any shift toward Office Scripts for web scenarios.

Which VBA Core pattern ranks just above this one at #47?
expand_more

The pattern one rank above is “VBA Shell and Wait with Exit Code”. If your use case overlaps, compare both before committing.

Data source: Community-verified Q&A snapshot. Q-score 3, Answer-score 13, original post 2012, ranked #48th of 95 in the VBA Core archive. Last regenerated April 14, 2026.

vba