What's the default set of dependacies with vb6?

I have made a simple app to calulate UK VAT. It has 1 form. After I created the .exe file, I ran pdcmdln.exe (Package / Deploy). This created... setup.exe, vat.cab, set.lst and a folder named 'support'. In total they are nearly 12 meg which seems way too high for such a small app doing such a simple task.

During the Package / Deploy process I got a few windows about dependancies and being unsure what was needed, I left them all at the default. One mentioned my app using ODBC which as this is database related why would it be a dependency in my app?

Anyway, my question is, which of these 12 meg worth of files do I give to someone else for them to be able to run the app? Or maybe I should go through a re-package and make changes to dependencies / deselect certain dependencies?

Before I began using VB, I understood that in order to run a vb6 created app, that all I needed was the vbrun60.exe package. Can someone explain what the requirements are for both the vbrun60.exe files plus other dependecies please.

Thanks.

The dependency files differ from project to project.

If you have loaded anything from the Components list into your project, then the OCX file that houses the control you used must be included with your setup package.

Any files used as references must be included in your setup package.

Providing a specific list for a specific project without knowing what is in the project is speculative at best.

It has no referenced files. As I said its a single form with simple maths on it. Calculating VAT (or any tax) is a simple fomulae.

There is a single input field, a fixed rate field and 2 outputs (Net / Gross).

VB Code:

VAT = NetAmount * VatRate
GrossAmount = NetAmount + VAT

Maybe the form had componants on that weren't used. I didn't even realise if componants they were on the toolbar that they would become dependencies (even if unused). Thanks.