SCA Computing home
About Us Public Transport Management Software Sales And Marketing Software Language Software And Translation Other Projects

Importing Data


If the configuration of the existing or archive data matches MarketForce! quite closely (a perfect match is not required), the program can work directly on it.
If the user prefers to create a separate marketing database from existing sales data, MarketForce! can import the existing data into a new Access database. In this case, customer records can be de-duped at the same time.
In both cases, key tables, and key fields within those tables, are matched. See below for a view of the table-matching/import process from a SQL public transport ticket sales database to MarketForce:


Importing an SQL database

The number and names of fields in the source database and the MarketForce! environment do not need to match completely. The example below shows the match being established between Microsoft's sample Northwind database and MarketForce!.


Matching fields in an existing database

Apart from three basic tables, for customer data, order data and product data, MarketForce! only uses those tables which are actually available. The same applies to fields: in this example, the Title, First name, Address lines 3 & 4 and Date of Birth fields in the customer data table are ignored.
If no promotional campaigns have been run, MarketForce! functions referencing campaigns are disabled.