Looking for suggestions

I am thinking about writing a niche market accounting application with several modules (Accounts Payable, Accounts Receivable, G/L, etc) in Visual Basic 2010. The back end database is going to be SQL Server. What I am wondering is would it be best to make this application into 1 single large "exe" file, or into many smaller ones, say one for A/P, one for G/L, etc etc.?

I have never written anything on this scale (in vb anyway, in mainframe languages I have and its all in different files)

Anyone?

One exe that references multiple assemblies

I'd go with the modular approach to this as well.

-tg

Thanks for the replies. Excuse my ignorance but could you clarify what you mean by referencing multiple assemblies?

He means, create one class for each functionality (Accounts Payable, Accounts Receivable, G/L, etc) .
The class would get compiled to a separate DLL files.

That's what I understood.