suggestions for project with lots of code

[geek4h]

I would like some suggestions.
* This is an internal application in which the data files are small
* But the VB code portion is relative large
* Users will be emailing the data around and I don't want to have 5M files when I can get by with 50K files
* Suggestions on the best way to seperate the code from the data

For example: But all the code in an add-in, DLL, or COM? What would be best one do work with?

 

[zilpher]

I'd be intrigued to know how you differentiate DLL and COM in this respect.

At the sake of security, an addin is the simplest way to achieve what you are looking to do. It is no more or less secure than having the code in your workbook but is easier to manage because you maintain one version of the code, if you need to change it you simply release a new version to everyone and don't have to worry about there being any workbooks that need the new code applied.

If you want better security, an ActiveX dll written in Office Developer or VS is an option. This is of course a COM object and as such is 'compiled' and inherently more secure.

The other option is a database application, assuming Excel is just acting as a data repository, removing the need for your users to email workbooks to each other.

You could do it either with some client software written in a language of your choice, or a browser based application. You'd be looking at a combination of:

Client/Server:
VB/C++/Your Choice
MySQL/MSDE/SQLServer/Oracle/you name it

Browser Based:
SQLServer/IIS/ASP (.net if you fancy it)
MSDE/IIS/ASP (.net if you fancy it)
MySQL/Apache/PHP
Probably a myriad of others....

My personal preference would be MySQL/Apache/PHP for several reasons:

Centralised code, no distribution problem
OpenSource/low cost
Cross platform Support (run it on a windows or *nix host)

HTH