DLL is possible with VBA ?

[jon_sg]

Does any one know if it is possible to create DLL's with VBA? If so can anyone recommend a good site or book for instructions on this.

I have an MS Office application that sits on our server it is properly registered within the windows registry and all works fine.
The application consists of MSDE backend database and draws contact information from Exchange server, Project details from various MS Project files. All data transfer and a lot of validation is handled by ADO in a series of VBA class modules and collection classes. Reporting and data entry is done from an Access application and Excel, Project and Word templates. It is fully tested, debugged, secured and works fine.

Unfortunately Little Hitler in the head office IT dept has informed us that storing all of the class modules in a seperate access database is not secure, against company policy and we have to put them into encrypted DLL files. We are not programmers and built this application relying heavily on Access Developers Handbooks and VBA Developers guide and have absolutely no idea how to go about creating DLL or other library files any ideas would be greatly appreciated, even if it is to 'Seek Professional Help?"

Regards

Jon

Sorry: The Class modules were created in VB Editor and expotred - they are stored in a folder on the server /classes as .cls and .bas files. With no access from clients.

 

[namliam]

Easiest way is to convert your db to MDE, which is much more secure than an access MDB.
It still will require (at least) a run time version of Access to work, but you cannot get at the code (you might need to tweek one or two settings).
Read all about it in the manual.

Regards

 

[jon_sg]

Thanks, I suppose we could always put a copy of Access onto the Server.

 

[namliam]

No need, you need access (run-time) on the client not on the server.

 

[jon_sg]

No need, you need access (run-time) on the client not on the server.

Thanks a lot for your help, I never even thought about MDE files, amazing how I missed the obvious. But I still think the server for is the place for it

My plan is
Put the modules into Access and compile it as an MDE file with password. Put it on the server I will still be able to use the path to access it from the application on the client machines? Hence no need to install access on all the Client machines. alright it wouldn't be an encrypted DLL but certainly alot better than .cls files in a folder. Probably make it run faster too!
Changing all the paths and altering the registry may be bit of a ball ache!

Regards

Jon

 

[Pat Hartman]

I'm having a little trouble here. If you're working with an Access application what are you doing with .bas and .cls files? Those are VB files and have nothing to do with Access. You say you are working with VBA which is what the office products use. It doesn't stand alone. Are you sure you didn't develop a VB application and just used Access to store your data?

 

[modest]

What I've come to realize is that Pat Hartman is a genius in Access.
... enough said.

he is right VBA is just Visual Basic for Applications, and if you are using .bas and .cls files, how are you implementing them into your database. More importantly, what are you using them for.

 

[jon_sg]

We wrote all the modules in the MS VB Editor supplied with office exported them and used a freeware VB compiler. So I suppose you could say that it is VB rather than a VBA one; even though the application is purely Office programs and a third party MS Project viewer.
We couldn't find a freeware or reasonably priced compiler that compiled DLLs with 128 bit encryption. When I wrote the initial request I was wondering if anyone here knew a way of doing this using VBA or third party compiler but I believe . I didn't want to have to purchase Visual Studio.net at about $800 just to compile four DLLs the code for which is already written.
Mailman came up with a good idea using MDE files. Having had no experience of using Access MDE files I am on reflection a little reluctant to try this, especially if it may mean installing access on all 35 client machines to work.

Regards

Jon

 

[modest]

First of all I have Visual Studio.NET and I don't think it costed me $800

Second, you should try Microsoft's site, sometimes they have beta tests and other free compilers for download (free of charge unless you request to get it on cd).

Third, you don't need the whole studio, you more than likely just need VB if I'm not mistaken. Most bookstores sell microsoft books that come with VB. Additionally, you can just by the VB solo edition, but I'm really surprised Ms doesn't have a VB compiler for free on their site.

In regards to MDE, I'm not to that point yet. I'd rather just gloat in what I know then to idolize what I don't. But that's the great thing about life: you go an inch, but have to run a mile.

 

[Rich]

He is right

That's a She, by the way

 

[modest]

Thank you for the update, my apologies Pat. I made the edit above.

This reminds me of the Saturday Night Live skit with "Pat" where they don't know if it's a guy or girl

 

[Cosmos75]

Maybe these links might help?
- How To Create Office COM Add-Ins by Using VBA and Office Developer

More info here...
- Add-ins, Templates, Wizards, and Libraries

I'll be honest, I have Office XP Developer Edition and have tried to make a .dll file but have NO IDEA how to do it. I've got a function that I want to create a .dll file so I can call it from Access or Excel but it seems like there is more to it than just having created a VBA function.