Standard EXE vs. COM-Based application

Hi,

I have many computers that connect to each others in a LAN and WAN network. In that network I have a server and a database server. I would like to build an application that allow users retreive and update data on the servers from/to their computer. But I don't know what solution should I choose in the following solutions:

1. I should build a standard EXE that can connect to the Database server from remote machine and then deloy it on the other computers.

2. I should build a client-server COM-based Application that have server components (deloy on server) and client components (deloy on client).

Could you please give me an idea? and tell me what is benefit that I can get from these solutions? What is difference from these solutions?

Thanks in advance,

Trung Luu

hi,
Microsoft have a solution for u and it calls DNA.
DNA stands for Distributed Internet Application.
it is a complete methodology of how to create a distributed application, either in LAN or WAN.
the idea is to separate the application into logical tiers (or layers).
in general, u have one tier for the user interface, one for bussines logic and one for data source(s). u may add as much tiers as u like.
according to your requirements (the clients can reside in a LAN or WAN), i think that the best solution for the user interface will be web based (ASP, HTML etc.).
the bussines logic r COM objects running under COM+ and the data layer consist mostly of stored procedures.
when u separate your application u gain:
1. very flexible maintains. for instance if u need to modify some bussines rule in the bussines logic DLL's or add something to one of the stored procedures, u don't have to redeploy the entire application to the clients.
2. all the access to the data sources r in one place, so:
A. u open connection and close it at one place - don't have to concern whether u forgot to close a connection or not.
B. COM+ and OLE DB gives u connection pooling automatically - improving performance.
C. if u decide to work with a different data source - u only have to change it in one place.
D. u don't have to pay for lot of connections.
3. u can have both web based user interface and windows GUI. u don't duplicate the other tiers.
4. if your user interface is web based, you don't have concern about deployment at all.
there r more reasons why u should build your app in DNA concept.
u can also consider moving to .NET, because the new architecture gives u further capabilities for building distributed applications.

Hi Deja,

Thank you for your information

Trung Luu