Data File Structure / Content

<< Click to Display Table of Contents >>

Navigation:  MLS 2026 Installation and System Setup > Datamanager - Your Installation and Data Management Tool > The MLS File Editor >

Data File Structure / Content

 

Data File Structure & Content

The MLS 2026 File Editor provides direct access to the database files used throughout the system.

These files use the industry-standard:

.DBF

format and may be read by many third-party programs and reporting tools.

⚠️ IMPORTANT

Although many external programs can read .DBF files, extreme caution must be exercised when working with them.

Some programs that claim to support database editing may:

damage indexes

alter headers

corrupt memo fields

or permanently destroy data integrity

For this reason:

NEVER directly modify live MLS 2026 database files using external software.

Always work from copies of the data.


What Is A Data File?

A data file contains the information entered into the system by the users.

Examples include:

clients

vehicles

workorders

inventory

appointments

accounting entries

and scheduling data

Most software systems organize information into:

databases

tables

records

and fields

MLS 2026 stores information using:

independent database files

rather than one large combined database.

Each primary data file ends with:

.DBF

These structures originated with the early:

dBase

database systems, but MLS 2026 uses modern:

32-bit FOXPro-compatible database structures

including:

.DBF data files

.FPT memo files

.CDX index files

Programs that do not properly support:

DBF / FPT / CDX

structures may:

corrupt data

destroy indexes

damage memo relationships

or make files unreadable


Components of a Data File

Each MLS 2026 database file contains several important elements.


Header

The first section of every file is called the:

Header

The header contains:

field names

field types

field sizes

and record counts

The program reads the header first to determine:

where records are located

how large they are

and how to interpret the information stored within the file


Records

Database files are divided into:

records

A record represents one complete entry within the file.

Examples:

one inventory part

one client

one vehicle

one workorder line

one appointment

Although records appear separate logically, they are actually written:

as one continuous stream of information

The header information tells the program:

where records begin

where they end

and how to separate them properly

Some files may contain:

only a few records

while others may contain hundreds of thousands


Fields

Each piece of information within a record is stored in a:

field

A field has:

a name

a data type

and a maximum size

Data entry screens display the information in a user-friendly format, but internally each field is strictly defined.

MLS 2026 uses several field types.


Character Fields

Character fields contain:

letters

numbers

names

addresses

descriptions

notes

and codes

These fields are usually fixed-length.


Numeric Fields

Numeric fields contain:

numbers

quantities

prices

totals

balances

and values used in calculations

Numeric fields also specify:

total field length

and decimal precision


Logical Fields

Logical fields contain:

True / False

Yes / No

type information.

These fields act as switches or flags.


Date Fields

Date fields store:

service dates

due dates

invoice dates

appointment dates

and elapsed time calculations

Date fields are always stored in a standardized format.


Memo Fields

Memo fields contain:

long text

recommendations

notes

service descriptions

and extended information

Unlike character fields:

memo fields are variable length

One record may contain:

very little information

while another may contain several pages of text

Memo contents are stored separately in:

.FPT

files.


Field Sizes

Most fields have fixed lengths.

Examples:

Character fields vary by definition

Logical fields are always length 1

Date fields are always length 8

Memo fields use references rather than fixed storage lengths.


Supplemental Uses of MLS 2026 Data

The MLS 2026 database structure is extremely powerful and allows information to be used for many additional purposes.


Merge Data

Data may be copied into:

merge files

spreadsheets

mailing lists

or word processing documents

This is commonly used for:

marketing

client communications

mailing labels

and specialized reports


Spreadsheets

Data extracted from MLS 2026 may be imported into spreadsheet programs such as:

Excel

LibreOffice Calc

or Google Sheets

This allows:

projections

trend analysis

pricing studies

budgeting

and management forecasting

Examples:

analyzing sales growth

projecting inventory increases

evaluating labor trends

modeling pricing adjustments

Because the information already exists in MLS 2026:

duplicate data entry is eliminated


Graphics & Charts

Spreadsheet and reporting systems may also generate:

graphs

charts

visual summaries

and business analysis reports

Once data is extracted into tabular form:

graphical tools can quickly present trends visually


Custom Reports

Many commercial reporting tools can directly read:

.DBF / .FPT

structures.

One commonly known product is:

Crystal Reports

These tools may be used to create:

management summaries

specialized invoices

productivity reports

accounting analysis

inventory movement studies

and many other custom documents

Instructions for creating custom reports are provided by the reporting software itself.


Important Operational Guidelines

⚠️ ALWAYS create a full backup before working with data files.

⚠️ NEVER experiment on live production files.

⚠️ NEVER allow unknown third-party utilities to directly modify MLS 2026 data.

⚠️ NEVER assume all .DBF editors properly support FOXPro-compatible database structures.

Data integrity is one of the most valuable assets of your business.

Protect it carefully.