Database with COM objects

[Endeavor]

Hi, I am new to this board and to COM objects. I am trying to create a COM that uses a Access Database.

I can create the COM with a connection to a database, but I want to be able to embed the database inside the COM. Is that possible?

To be more specific, I don't want to package the database along with the COM object.

Thank in advance..

[razzaj]

using the PAckage and deployment wizzard you can add as many files as you want to package with the COM DLL , so you can select your DAtabase file abd it will add it to your PAckage.

[Endeavor]

Thanks for your reply, but that is NOT what I am looking for..

I can package the database with the project, but that means the database is a seperate file, and in the program I have to have a "outside" referernce to it... which I don't want.

The main reason for this is I don't want user to be able to view my database.

I found that I can do something with reference files, but don't know how to do it. If you can help me with that, that would be great.

thanks again

[robinm]

Why do you want to 'embed' a database inside a com object.


1stly you can't

secondly what is you definition of COM ?

What are you trying to do with the project ?

Are you referring to and axctiveX.dll ??

Or a VBproject of some sort.

COM or the Component Object Model is a specification.
The COM standard defines the following;

A common way for applications to access and perform operations on Objects.

A mechanism for keeping track of whether an object is in use and deleting it when it is no longer needed.

A mechanism for applications to exchange objects

A way to identify objects and to associate them with applications that understand how they are implemented.

(excerpt from DAN APPLEMAN - Developing COM/ACTIVEX Components

[robinm]

If you don't want you user to see your database, why don't you just lock it down with user password and names ?

Idea behind 3 tier architecture : >


GUI(User end)------->Business Layer(rules etc) ------> Database(DB)


The COM objects for the database end are usually the components that carry out all the data access to and from the database. ie
Add/UPDATE/DELETE etc.
The database could be on a physically different server to the COM object. The user need never know where the database is.
If this is a single user system, then the simplest answer would be to use access security to lock it up.

Hope it helps. Any questions mail me.