VBACODE.AI / DOCUMENTATION

Excel VBA user guide

Generate from text or read existing source, understand the issue and complete clear requests directly. Learn how to provide essential context, download a copy and report runtime results.

Open VBA workspace →

Can I generate macros without an Excel file?

Yes. Describe the repeated steps, input layout, rules, output and trigger. For example, sum amounts by customer and update the result with a button. Send your request to generate a downloadable .xlsm directly when its requirements are clear. No empty workbook upload or manual source import is needed.

Attach an existing .xlsx or .xlsm when adding macros while preserving data and formulas. Repair and modification can begin with pasted source and errors; preserving original data, buttons and unrelated macros in a download requires the original workbook. Explanation can start with pasted code alone.

Run the downloaded macros

Open the downloaded .xlsm copy in desktop Microsoft Excel. Existing buttons normally keep their original procedures. New entrypoints and run steps appear in the conversation result.

On Windows use Developer → Macros or Alt+F8 for callable procedures. On Mac use Tools → Macro or Developer → Macros. Worksheet events should be triggered as described rather than manually run as ordinary macros.

Provide a folder, file or parameter locally if the macro prompts for it. Canceling selection should preserve data. A generated file and source checks do not establish desktop compilation/runtime testing; test a copy. Allow only macros whose source and purpose you understand.

What this workspace focuses on

Excel VBA generation from concrete steps, error diagnosis, existing-source repair, behavior changes, entrypoints and read/write explanations. Work can start from text or your workbook and preserves data, unrelated macros and existing button bindings.

An .xlsx can receive a standard macro for a specific repeated operation. Required sheets, cells, formulas or buttons support the macro task. General cleaning, standalone formula generation and building complete business applications are not the main service; specify the concrete automation workflow.

Describe, complete, download and continue

1. Describe generation, repair, modification or explanation, or click a suggestion to fill the composer. Generation can start with text. To repair your workbook, attach the .xlsm and describe the action, error and expected result. We read available source and workbook facts before asking you to repeat information.

2. After sending, the center shows your messages, actual activity, findings and the plan in one conversation. Use Table preview to inspect cells; click, drag or Shift-select ranges and reference them in your message.

3. Answer essential questions in the same composer. If concrete choices are available, click one to fill the composer, then send. Information that can be selected when the macro runs is listed separately; local target files do not need uploading now.

4. Clear, fully supported requests execute directly after analysis for 10 credits, with the cost shown before sending. Failed execution is refunded. Explanation uses analysis allowance without an execution charge. Acknowledged unsupported features may have explicit partial acceptance; essential unanswered questions cannot be bypassed that way.

5. Download and run as instructed. Report remaining errors, trigger steps and results to continue using the current file and prior context. Requests are limited to 12,000 characters and never silently truncated.

When will more information be needed?

The model first inspects source, sheets and your messages. Available path rules, field mappings and procedure facts are not requested again. Missing expected behavior, calculation rules or source/destination choices require a specific question.

For broken links after changing computers, a fixed username can be replaced with an appropriate path rule, and colocated files can use the workbook directory. A genuinely unknown new folder can be selected when the repaired macro first runs. The website cannot browse your local folders; target existence is checked locally, and fixing a path cannot restore a missing file.

Why attach a second workbook?

After starting a task, add a workbook as a macro source, data-structure reference or explicit destination. State the relationship and destination before sending. An unclear destination requires a question.

Upper Table preview tabs switch files and lower tabs switch sheets. Previewing a file does not change the destination. Standalone module copying requires checks for names, sheet references and dependencies. This is not a general multi-file merge tool.

Windows, Mac, WPS and the web

VBA targets desktop Microsoft Excel. Mac Excel supports VBA subject to dependencies; Windows COM, system APIs and external components may be unavailable and must be disclosed.

Excel for the web cannot run VBA. Mac WPS JS macros are not VBA. Compatibility depends on the actual source and software version.

Files and verification limits

Supports unencrypted .xlsx/.xlsm, up to two files and approximately 4 MB combined upload. Up to 512 modules / one million source characters can be read, with 100,000 characters per changed module. Sheet reading is bounded at 20,000 rows, 128 columns and 200,000 cells overall.

Locked projects, signatures, UserForms/ActiveX, Access artifacts, .xls and .xlsb are not supported for automatic writeback. Existing legacy controls/comments are preserved and cannot simply be overwritten or rebound. Unsupported parts should have a specific explanation.

The model understands and writes source; backend tools extract, save and verify it without executing VBA. Generated files, source checks and desktop runtime acceptance are separate statuses. Unexecuted macros are not described as successfully run.

History, files and credits

Original/result files, drafts and local conversation rounds are cached in this browser per task. Another device or cleared browser storage may require reattaching the original and second workbook to continue or download. Tasks expire after 24 hours.

Open credits and usage beside the account avatar; ledger and purchase flows remain on the credits page. Free analysis: 10 lifetime; Starter/packs: 150 per month; Pro: 400 per month. Automatic execution costs 10 credits and failed execution is refunded.