www.theplague.fora.pl

clkelyqld2

Article Source: uPublish.info
E.Kalai Kavitha Article Feed :
**NOTE** - has claimed original rights on the article "Customer Relationship Management System Based on ActiveX Data Object with Framework Technology" ... if there is a dispute on the originality of this article ... please contact us via our and supply our staff with the appropriate details of dispute (ie ).
References:
About the Author:
Category:
Keywords: , , , ,
Introduction:
For the staff of [url=http://www.piktor.fr/hollister-france/]hollister france[/url] SEM, in addition to qualifications and skills, the connection of persons is an important determinant of private career and business development. The improvement of enterprises can be decided by interpersonal scope and depth of the breadth of his career; while some staff has a good network of resources, but his relationship has never been collated and utilized. In market competition, how to seize opportunities, how to keep work and family harmony, how to expand their network, how to develop and maintain their own network of people has become an important job for each employee. In this paper, to build the core competitiveness of SME, ADO.NET technology and CRM system are used to construct the framework. Through the development of a comprehensive and meet business, the employee relationship management system can be built.
II. DEFINITION OF CRM
CRM (customer relationship management) is an information industry term for methodologies, software, and usually Internet capabilities that help an enterprise manage customer relationships in an organized way. For example, an enterprise might build a database about its customers that described relationships in sufficient detail so that management, salespeople, people whom provide service, and perhaps the customer directly could access information, match customer needs with product plans and offerings, remind customers of service requirements, know what other products a customer had purchased, and so forth. According to one industry view, CRM consists of:
?- Helping an enterprise to enable its marketing departments to identify and target their best customers, manage marketing campaigns and generate quality leads for the sales team.
?- Assisting the organization to improve telesales, account, and sales management by optimizing information shared by multiple employees, and streamlining existing processes (for example, taking orders using mobile devices)
?- Allowing the formation of individualized relationships with customers, with the aim of improving customer satisfaction and maximizing profits; identifying the most profitable customers and providing them the highest level of service.
?- Providing employees with the information and processes necessary to know their customers, understand and identify customer needs and effectively build relationships between the company, its customer [url=http://www.piktor.fr/hollister/]hollister[/url] base, and distribution partners.
III. THE MANAGEMENT PURPOSES AND PRINCIPLES OF SMES [url=http://www.piktor.fr/doudoune-moncler/]doudoune moncler[/url] CUSTOMER RELATIONSHIP DESIGN
A. The management purposes of SMEs customer relationship design
1) Achieving information collection and management of custom during the course of the operation can be accumulated a lot of customer dates of enterprises for SME. Because of its many loopholes and manage non-standard place, it will be found that some of the data is incomplete, even some of the data is completely useless from the perspective of customer relationship management analysis, for example, only have database of customers who buy products, data. The product usage problems and customer evaluation of products are very little or no data from the customer purchased the product.
Lack of these dynamic processes dates, small businesses can not accurately grasp the needs of customers and cannot provide customers with more targeted services. Therefore, for SME, customer information collection and management are extremely important.

2) Marketing activities of achieve customer information management
CRM systems can be established by companies market to support the development of the program of activities. Before market events, operations decision support analysis to determine market segmentation, customer investment preferences, investment in customer habits and so on. Selection of customers organize marketing activities can be decided by the relevant staff and analyzing.
Market activities, assignments, performance, revenues, expenses are all included in the management of customer relationship management product range to control the process of market activity. Through in-depth analysis of market activity, data mining will provide decision making for customer development, customer service and customer care.
3) Achieving customer service of management
Customers' purchase and use enterprise products are bound to request companies to provide services (such as product installation, product guide, technology upgrades, etc.), [url=http://www.jeremyparendt.com/Barbour-Paris.php]barbour france paris[/url] and will inevitably lead to discontent.
How to timely and effectively services to customer. How to minimize these customer's complaints and How to enhance the efficiency [url=http://www.meekrei.com/cgi-bin/aska/aska.cgi/?c=search&/./aska.cgi?mode=resmsg&no=585]abercrombie milano Newlywed G[/url] of communication with customers. Though CRM system these problems should be able to get a better solution.
B. Design principles of SME customer relationship management system
1) Meeting the internal demand
CRM system to satisfy the business enterprise department first demand should be satisfied though especially some main department, like marketing, sales and customer service department.
More specifically, marketing department conduct market activities management, follow-up and feedback are supported by CRM system, activities and obtaining the customer the evaluation form, distribution, discussing the information such as customer behavior to the customer, state classification; Supporting the sales department, and putting forward the sales task assigned to a task, evaluation and measure sales, and making the customer service department to be the system to provide for the customer service of accurate information, to ensure that the service center can treat customers consistent are also supported by CRM system.
2) Connecting the enterprise and market
CRM must collect the enterprise market, sales and service, a collaborative up marketing, sales and service of the communication channel between, solve the enterprise in the process of the real-time information and meet channel optimization.
Only in this way the analysis data real-time can be transferred to the sales and service department, so as to better understand customer behavior, keep old customers; In addition, the sales and service department of information gathered in the transfer market department to order to sales, service and complaint information analysis, and to work out in time more effective competition strategy.
IV ADO.NET Database Technology
ADO stands for ActiveX Data Objects and it relies on COM whereas ADO.NET relies on managed providers defined by the .NET CLR (Common Language Runtime). ADO.NET provides consistent access to data sources such as SQL Server, as well as data sources exposed through OLE DB and XML. The rapid development of web applications makes software development companies review the existing methods of working with data sources and adapt them to the web application specifications. The unpredicted growth of the number of clients makes web developers move from client-server to three-tier architecture, which sometimes brings out problems. Databases are unable to support the unlimited number of active connections limiting the availability of the site and causing losses. The ADO.NET (ActiveX Data Objects) technology can solve these problems and at the same time keep convenience and simplicity of programming.
The ADO.NET Data Platform is a multi-release strategy to decrease the amount of coding and maintenance required for developers by enabling them to program against conceptual entity data models. This platform includes the ADO.NET Entity Framework and related technologies.
ENTITY FRAMEWORK
The ADO.NET Entity Framework is designed to enable developers to create data access applications by programming against a conceptual application model instead of programming directly against a relational storage schema. The goal is to decrease the amount of code and maintenance required for data-oriented applications
Entity Data Model (EDM)
An Entity Data Model (EDM) is a design specification that defines application data as sets of entities and relationships. Data in this model supports object-relational mapping and data programmability across application boundaries.
Object Services
Object Services allows programmers to interact with the conceptual model through a set of common language runtime (CLR) classes. These classes can be automatically generated from the conceptual model or can be developed independently to reflect the structure of the conceptual model. Object Services also provides infrastructure support for the Entity Framework, including services such as state management, change tracking, identity resolution, loading and navigating relationships, propagating object changes to database modifications, and query building support for Entity SQL
LINQ to Entities
LINQ to Entities is a language-integrated query (LINQ) implementation that allows developers to create strongly-typed queries against the Entity Framework object context by using LINQ expressions and LINQ standard query operators. LINQ to Entities allows developers to work against a conceptual model with a very flexible object-relational mapping across Microsoft SQL Server and third-party databases.
Entity SQL
Entity SQL is [url=http://www.cod-esports.fr]abercrombie france[/url] a text-based query language designed to interact with an Entity Data Model. Entity SQL is an SQL dialect that contains constructs for querying in terms of higher-level modeling concepts, such as inheritance, complex types, and explicit relationships. Developers can also use Entity SQL directly with Object Services.
EntityClient
EntityClient is a new .NET Framework data provider used for interacting with an Entity Data Model. EntityClient follows the .NET Framework data provider pattern of exposing Entity Connection and Entity Command objects that return an EntityDataReader. EntityClient works with the Entity SQL language, providing flexible mapping to storage-specific data providers.
Entity Data Model Tools
The Entity Framework provides command-line tools, wizards, and designers to facilitate building EDM applications. The EntityDataSource control supports data binding scenarios based on the EDM. The programming surface of the EntityDataSource control is similar to other data source controls in Visual Studio.
Advantages and innovations in ADO.NET technology
-Using the disconnected model for accessing the data. ADO.NET application development technology offers an [url=http://gaoyusong.com/?p=73#comment-258927]UFO Spotted Over Overland Park in 2004 - written by Mark Fisher[/url] alternative to a traditional data access model. Normally, client-server applications use the technology of access to the data source where the connection with the base is maintained all the time. However, after the wide spread of the Internet based applications some vulnerabilities of this approach have been discovered. The experience of web developers has shown that the applications with the constant connection with the data source are difficult in scaling. All these problems are produced by the constant connection with database and are solved in ADO.NET. ADO.NET technology makes use of another data access model. ADO.NET access model establishes the connection only for some limited time when it's necessary to take some actions with the [url=http://wheretobuyparacord.com/new-butterfly-knife-with-ram-horn-handle-excellent-performance-high-quality-reliable.html#comment-1150]Why Should You Consider Unlimited Cell Phone Plans - written by Cullen Nedrich[/url] database. Thus, ADO.NET allows sidestepping these limitations of web application development process.
-Data string in the Dataset objects. In general, Dataset is a simplified relational database and can perform the most typical for these bases operations. Owing to ADO.NET application development technology, in contrast to Recordset, we can store several tables in one DataSet as well as the relations between them, perform the operations of selecting, deleting and updating the data. ADO.NET gives an opportunity any minute to get the latest information from the database using the call function FillDataSet. Thus, ADO.NET application development technology makes DataSet extremely convenient for most web applications. ADO.NET application development technology allows us to extract the data from the base and somehow handle it whenever it is necessary.
-Deep integration with XML. XML, a widely spread language, plays an important role in ADO.NET and brings some more benefits to ADO.NET application development technology in comparison with the traditional approach. It isn't necessary for a programmer working with ADO.NET to have the experience of working with XML or the knowledge about this language. ADO.NET makes all the operations transparent for web developers. XML (eXtensible Markup Language) represents an industrial standard supported by practically any modern platform, which allows transmitting data to any component that can work with XML and can be executed under any operating system. Thus, deep integration of ADO.NET with XML provides .NET application developers with ample opportunities.
Many application developers have already noticed the simplicity and convenience of the ADO.NET technology. ADO.NET application development technology provides an intuitive interface and logical set of objects. All these features make ADO.NET more appealing to .NET web developers.
ADO.NET Interfaces
The architecture of ADO.NET allows you to work directly connected to the database or in a disconnected manner. In the connected model a .NET framework Data Provider is used for connecting to a database, executing commands, and retrieving results. On contrary, the DataSet and Data Adapter components are the core of the disconnected model. A reflection is that the API in the connected model is quite similar to Java's JDBC.
CRM system is designed by database of connecting between the ADO and SQL Server link, which constitute ADO.Net library contains the following basic interfaces:
Connect to the database
Let's get started! First of all you must have a Data Provider installed for your database. The Data Provider is responsible for communicating with the underlying database. When working with Mimer SQL the Data Provider for ODBC that ships with .NET framework 1.1 can be used. The base classes for working [url=http://www.paolofranco.it/scarpe-hogan/]scarpe hogan[/url] with the Data Provider for ODBC are OdbcConnection, OdbcCommand, OdbcDataReader and OdbcTransaction. They are all found in the System.Data.Odbc namespace.
When you are programming with ADO.NET you work directly towards the Data Provider, so if you switch to another target database you must change [url=http://www.diecastlinks.co.uk]hollister uk[/url] your code and recompile. The different providers have the same functionality so the change is rather small, but it is still a major runtime limitation.
Before you can access the database you must create a connection to it. When working with the Data Provider for ODBC we use the OdbcConnection class to create a connection to the database. A connection string is used to tell the system which database to access. The string has the format:
"DSN=odbc_datasource_name;UID=database_ident;PWD=password"
You can pass the connection string through the constructor for OdbcConnection or you can set the ConnectionString property on an already created object.
When the object is created, the connection can be opened with the Open() method. When you are done you close it with the Close() method. A simple example might illustrate this (in C#):
using System;
using System.Data.Odbc;
. . .
OdbcConnection con =
new OdbcConnection("DSN=store_db;UID=BOOK_STORE;PWD=store");
con.Open();
//Do your database stuff
con.Close();
As you can see, this really doesn't do anything. It only connects to the database and then disconnects.
Executing commands
When you want to pass SQL statements to the database for execution you use the OdbcCommand class. In contrast to JDBC, ADO.NET only lets you have one type of command object. This object can be used for direct execution, prepared execution and for calling stored procedures.
Before you can use an OdbcConnection it has to be associated with a connection. This can be done either with the constructor for OdbcCommand or by using the CreateCommand() on the connection to create it. The SQL to execute can be provided in the constructor as well, or by setting the CommandText property on the command.
When the command is created we can [url=http://www.piktor.fr/louboutn/]louboutin[/url] call ExecuteNonQuery(), ExecuteScalar() or ExecuteReader():
-ExecuteNonQuery is used to execute a statement that doesn't return any result, like an UPDATE or INSERT. The number of affected rows is returned.
-ExecuteScalar() is used when only a simple result is expected, for example a statement like SELECT COUNT (*). It returns the first column of the first row and ignores the rest.
-ExecuteReader() is used to execute a statement that returns a result. We will take a closer look on that later on.
A simple example that inserts a row in the CATEGORIES table of the example database illustrates how to use the ExecuteNonQuery() command:
string sql =
"INSERT INTO CATEGORIES(CATEGORY_ID, CATEGORY) VALUES(12,'A category')";
OdbcCommand command;
command = new OdbcCommand(sql, con);
//An alternative approach
//command = con.CreateCommand();
//command.CommandText = sql;
//command.Connection = con;
command.ExecuteNonQuery();
As you can see, the above statement is using static SQL in a non-prepared statement.
Using parameters via a prepared statement is a convenient way to supply data for INSERT, and it can really boost performance since it reduces [url=http://www.batfriendtrust.it]hogan outlet[/url] the number of SQL compilations. After a statement is prepared it can be executed several times without compilation.
To set parameters for an OdbcCommand, simply add them to the Parameters collection. If you want to be able to control what datatype to use, create the OdbcParameter explicitly. Otherwise, you can simply add the value with a name identifying the parameter marker to the collection prior to Prepare(). The same example as above can look as follows:
string sql =
"INSERT INTO CATEGORIES(CATEGORY_ID, CATEGORY) VALUES(:id, :cat)";
OdbcCommand command = new OdbcCommand(sql, con);
OdbcParameter idParam = new OdbcParameter("id", OdbcType.Int);
idParam.Value = 12;
command.Parameters.Add(idParam);
command.Parameters.Add("cat", "A category");
command.Prepare();
command.ExecuteNonQuery();
Error handling
When working with databases, error handling is essential for proper application behaviour. In the above examples we have skipped that part completely. In ADO.NET, error handling is carried out using so called try-catch-statements.
Basically all database operations can throw an OdbcException that contains information about what went wrong. An error situation can cause several error messages to be generated. The simplest way to present the error is to show the OdbcException.Message, but that way we only get the first error. Besides the fact that we can have several errors in one OdbcException we can retrieve more error information if we use the OdbcException.Errors collection to get all the underlying ODBC errors.
A simple example that prints information about all errors we have in an exception is shown below:
try
{
con = new OdbcConnection("...");
con.Open();
. . .
con.Close();
}
catch(OdbcException oe)
{
foreach(OdbcError oErr in oe.Errors)
{
Console.WriteLine("Message: " + oErr.Message);
Console.WriteLine("Native error: " + oErr.NativeError);
Console.WriteLine("SQLState: " + oErr.SQLState);
Console.WriteLine("Source: " + oErr.Source);
}
}
Warning handling
To handle SQL Warnings we [url=http://www.mxitcms.com/abercrombie/]abercrombie[/url] have to write an event handler for OdbcInfoMessageEventHandler. To do this, simply write a method with the same signature as OdbcInfoMessageEventHandler and couple it to the connection. For example, in the general error handling class ExampleErrorHelper we can write the method HandleInfoEvents as:
public class ExampleErrorHelper
{
public void HandleInfoEvents(object sender, OdbcInfoMessageEventArgs e)
{
Console.WriteLine("An event was thrown")
foreach(OdbcError oEvent in e.Errors)
{
Console.WriteLine("Errors: " + oEvent.Message);
Console.WriteLine("SQLState: " + oEvent.SQLState);
Console.WriteLine("Native: " + oEvent.NativeError);
}
}
// Place other error handling stuff here...
}
The method is then coupled to the connection as:
. . .
ExampleErrorHelper eeh = [url=http://www.1855sacramento.it/peuterey.php]peuterey outlet[/url] new ExampleErrorHelper();
con = new OdbcConnection("...");
con.InfoMessage += new OdbcInfoMessageEventHandler(eeh.HandleInfoEvents);
This way, the HandleInfoEvents is called as soon as a warning is issued and the warning is printed.
Fetching the result
When we want to fetch the result of a query we use the OdbcDataReader class. OdbcDataReader is a fast, read only and forward only representation of the result and we get it by calling ExecuteReader() on a command. When we have the OdbcDataReader we can iterate through it using a while loop in conjunction with the Read() method:
. . .
OdbcDataReader reader = command.ExecuteReader();
Console.WriteLine("ISBN\tAuthor\tTitle");
while(reader.Read())
{
Console.Write(reader.GetString(0) + "\t");
Console.Write(reader.GetString(1) + "\t");
Console.WriteLine(reader.GetString(2));
}
reader.Close();
As you can see we iterate throw the OdbcDataReader by calling reader.Read() which moves the cursor one row forward. The reader.GetString(0) is used to get the first column and so forth. There are GetXXX() methods for most datatypes, but there is no equivalent method to JDBC's getString("columnname") - only the index can be used which is a pity. This way we depend on the column order in the SELECT statement.
Transactions
So far we haven't used explicit transaction handling and therefore auto-commit has been enabled. This means that all commands have been executed in their own [url=http://www.footdedemain.fr]jordan pas cher[/url] transaction, and that might not be what we want. Fortunately, transaction handling is quite easy and straightforward in ADO.NET using the OdbcTransaction class.
A transaction is started by calling the OdbcConnection.BeginTransaction(isolationlevel) that returns an instance of OdbcTransaction. The different isolation levels are available in System.Data.IsolationLevel. For example, System.Data.IsolationLevel.Serializable can be used.
All SQL statements that we want to be part of the transaction have to be associated with the transaction object. This can be done by passing the transaction through the constructor of the OdbcCommand or by setting the Transaction property. When we are done with the work we simply call OdbcTransaction.Commit() or OdbcTransaction.Rollback() to commit or roll back the transaction.
try
{
OdbcConnection con = new OdbcConnection("...");
con.Open();
//Start the transaction
OdbcTransaction trans =
con.BeginTransaction(System.Data.IsolationLevel.Serializable);
OdbcCommand command = new OdbcCommand(sql, con, trans);
//An alternative but equivalent approach
OdbcCommand command2= new OdbcCommand(sql2, con);
command2.Transaction=trans;
//Execute and commit
command.ExecuteNonQuery();
command2.ExecuteNonQuery();
trans.Commit();
con.Close();
}
catch(OdbcException oe)
{
//Show errors
try
{
trans.Rollback();
}
catch(OdbcException oe2)
{
//Show errors
}
}
As you can see, we simply commit when we are done and if an OdbcException is thrown we do a roll back. Note that the trans.RollBack() method can throw an OdbcEvent itself and is therefore surrounded by its own try-catch.
DataSet and DataAdapter
As we have shown above, working with ADO.NET directly connected to the database (the connected model) is quite similar to how we work in JDBC and ODBC. The DataSet and DataAdapter in ADO.NET are used to work in an entirely different way (the disconnected model).
DataSet can be thought of as an in-memory database, which we can be populated from a database or be created directly in the program. The internal format of the DataSet is XML, which enables for openness between different parts of the system. For example, a DataSet can be sent between components, XML can be sent to a DataSet to update it and data can easily be received in XML format.
The bridge between the DataSet and database is the DataAdapter, in our case an OdbcDataAdapter. A DataAdapter is a representation of a connection to the database and the SQL statements used to get and update data. The DataAdapter is used both for filling the DataSet and to update the database.
When you use this method of programming you never open or close connections of your own. You simply create a DataAdapter, supply it with a connection context and at least a SELECT statement. The DataAdapter is then administering the connection for us. When we fill a DataSet, the connection is made, the data is fetched and then the connection is closed immediately.
DataSets are useful when we want to send data between components, when we want to get the data in XML format and when we are developing GUIs. When developing GUIs there are several controls in the .NET framework that can be directly connected to a DataSet. With this model we can show a DataGrid connected to the database with a few lines of code.
A simple example that uses a DataSet to print the data in XML format is [url=http://www.lotogame.fr/hollisterfrance.php]www.lotogame.fr/hollisterfrance.php[/url] shown below:
OdbcConnection con = new OdbcConnection("...");
string selectSql = "SELECT CATEGORY_ID, CATEGORY FROM CATEGORIES";
da = new OdbcDataAdapter(selectSql, con);
ds = new DataSet("Categories");
da.Fill(ds, "Categoryitem");
Console.WriteLine(ds.GetXml());
As you can see above, we never open the connection ourselves. The output of the example is:

1
Music

2
Books

3
Video

4
d

Figure 1 shows the required classes and some relationships among them.

Figure 1 Some Relationships of Data Provider Classes
Comparison of purposed system(ADO.NET based) with Existing System(ADO based) CRM Database Technology
oADO works with connected data. This means that when you access data, such as viewing and updating data, it is real-time, with a connection being used all the time. This is barring, of course, you programming special routines to pull all your data into temporary tables.
oADO.NET uses data in a disconnected fashion. When you access data, ADO.NET makes a copy of the data using XML. ADO.NET only holds the connection open long enough to either pull down the data or to make any requested updates. This makes ADO.NET efficient to use for Web applications. It's also decent for desktop applications.
oADO has one main object that is used to reference data, called the Recordset object. This object basically gives you a single table view of your data, although you can join tables to create a new set of records. With ADO.NET, you have various objects that allow you to access data in various ways. The DataSet object will actually allow you to store the relational model of your database. This allows you to pull up customers and their orders, accessing/updating the data in each related table individually.
oADO allows you to create client-side cursors only, whereas ADO.NET gives you the choice of either using client-side or server-side cursors. In ADO.NET, classes actually handle the work of cursors. This allows the developer to decide which is best. For Internet development, this is crucial in creating efficient applications.
oWhereas ADO allows you to persist records in XML format, ADO.NET allows you to manipulate your data using XML as the primary means. This is nice when you are working with other business applications and also helps when you are working with firewalls because data is passed as HTML and XML.
V.CONSTRUCTION THE CRM SYSTEM OF SME
A. Basic framework of CRM system of SME
From above, the CRM system of SME module structure is shown in figure 2

Figure 2. Basic framework of CRM system of SME
The figure can see a more complete CRM system should be front-end system (customer interaction system), intelligence analysis system, and back-end system (enterprise information system) three system integration and integration. CRM is a kind of business strategy, its core is the customer as the center, realize the door value maximization guest and promote the enterprise competitiveness.
B. CRM system of SME staff custom relationship
Based on the above module structure, small and medium-sized enterprise staff CRM system structure is shown in table 1
TABLE I.CRM SYSTEM OF SME STAFF CUSTOM RELATIONSHIP
C. CRM system for SME
Through to the CRM system of SME structure we know the needs of the enterprises is what, through the staff individual CRM system we mastered the staff what customers, so that to employees as the foundation, the service enterprises for the purpose, we construct the enterprise CRM model, as shown in figure 2,
Figure 2. The model of CRM system for SME
The model includes three parts: the contact center, excavation center and business center. Contact center touch the customer, excavate center the customer information to input data excavation center, analyzes the data, to dig out the enterprise the useful information, and then excavation center [url=http://www.footdedemain.fr]jordan[/url] take the information to send to business center, carries on the corresponding processing. The business centers can feedback information to the customer. This forms a useful information circulation. Of course there are many specific treatment methods and technical details.
Customer information contained in the great value of customers, through analysis and mining information found the customer to trade the law of value, found that customers form law and so on can be deeply understand the demand of customer, and the enterprise correct decision, the promotion enterprise business level has important significance.
The main purpose of CRM system is to make the enterprise in the process of communication with customers, continuous improvement and customer information, and will be accumulated over the past or not collection of direct customer information to accumulate gradually, medium and small-sized enterprise business personnel, sales directors and decision makers can be convenient for the customer information query and analysis to find the target customers, explore potential customers, create sales opportunity.
For example: sales order is the customer or agent to buy the product certificate, which details the customer or agent buy kinds of product, the amount and quantity. According to the contents of the enterprise is order to complete the sale receipts, distribution and other business operation of the shipment. Order management of this function is mainly realize products quotation, generating order, order review, executive orders, order tracking, payment collection on the purpose, and automatic tracking order execution, when sales receipts close to the time limit, the system can automatically remind gathering; Owe, the system can appear on the electronic collection.
VI. CONCLUSIONS
SME survival state has always been more awkward, especially some of SME of our domestic now facing the global financial crisis, upgrading industries need a lot of capital and technology support. Technical innovation is not easy, but market competition is so fierce, so SME want to survive have to find their own core competitiveness, So using ADO.NET database building small and medium-sized enterprise CRM system, not only the full consideration of the small and medium-sized enterprises, the current situation of the enterprise and employees of personal relationships and enterprise customer relations combined, Let staff working at the same time the work of efficient and can own life into account, do work and family harmonious development.
(c)
Customer Relationship Management System Based on ActiveX Data Object with Framework TechnologyArticle Summary: Abstract-Implementation of Customer Relationship Management System (CRM) is the core competitiveness of Small and Medium Enterprises (SME) to build an effective means. In existing system of CRM uses ADO Technology without [url=http://www.achbanker.fr/home.php]hollister[/url] framework concentration. It contains some drawbacks; those are discussed in this paper. This proposed system is designed to overcome the existing system of CRM are discussed and analyzed in the paper; the CRM system module of its framework is given, while ADO.NET database technology to achieve CRM system is also discussed. The CRM system builds a great help in the relatio