Command-line options

You can customize the way Paradox launches and runs. For example, you can start Paradox with a clear desktop; you can start the application in its minimized state; or you can determine which directory appears when the system is launched. Below is a complete list of the options you can set. For more information on configuration settings see, PDOXWININI and the system registry.

Option	Behavior

-b	Prevents multiple instances of Paradox from being loaded. If Paradox is already running, the Paradox window is brought to the front. If you try to load Paradox more than once without changing the private directory, an error message tells you that the BDE could not be initialized.

-c	Starts Paradox with a clear desktop.

-d Filename	Specifies an alternate PDOXWORK.INI, which contains folder definitions for use with the Project Viewer. By default, Paradox does not use an .INI file to store settings, but you can create a file named PDOXWORK.INI in your working directory, and Paradox will read settings from it automatically.

-e 	Prevents writes to the system registry.

-f	Forces writes to the system registry.

-i Filename	Specifies an alternate PDOXWIN.INI file, which contains desktop settings. By default, Paradox does not use an .INI file to store settings, but you can create a file named PDOXWIN.INI and Paradox will read settings from it automatically.

-m	Loads Paradox as a minimized application. This is useful if you want to load Paradox but not work with it immediately.

-n	Prevents saving work and private directories on exit.

-o Filename	Alternate BDE configuration file. (All BDE-based applications must use the same BDE configuration file when running concurrently.)

-p Directory	Start with a different private directory than the one set in the system registry. Paradox stores its temporary tables in the directory you indicate with this parameter.

	If you do not indicate a full directory path (one with a drive letter), Paradox looks for the new directory with respect to the Paradox system directory.

-q	Suppresses the Paradox splash screen while it is loading.

-s	Prevents resizing of the Paradox window.

-t	Allows resizing of the Paradox window.

-w Directory	Starts Paradox with the specified working directory instead of the one saved in the system registry.

-y	Forces saving work and private directories on exit.

StartFile	Opens the specified document and performs its default action. Paradox looks in the current working directory for the specified file unless you include the full directory reference to that file.

	You can tell Paradox to open a file when starting (for example, a form or report) by typing the name of the file, along with any necessary directory information. This does not require a special option, but does require the file extension. After loading, Paradox opens the file and performs its default action. For example, Tables are displayed in a table window, forms are displayed in a Form window, scripts are run, and so on.

To start Paradox with one or more command-line options

1.	Click the Run command on the Windows Start menu.

2.	Type the path to PDXWIN32.EXE, type a space at the end of the path, and then type the option(s) you want to use.

You can also locate PDXWIN32.EXE by clicking the Browse button.

3.	If you use more than one option, separate each with a space.

Tip

  You can make permanent changes to the Paradox command line by adding one or more of the above options to its Windows shortcut path.
  
International (regional) issues

Paradox can be configured to work with a wide variety of international languages and data formats.

  Character set issues
  
  Sorting conventions
  
  Data formats
  
  Internal data conversion
  
  Preventing unsupported character conversion
  
Preparation and assumptions

Before installing Paradox in (or using tables from) an international setting, make sure of the following:

  The International settings of the Windows Control Panel correspond to your needs.
  
  You understand the differences between (and implications of) the Windows (ANSI) character set and your DOS (OEM) code page.
  
  You know how to use AKT and the numeric keypad to enter extended characters in Windows applications and files. (Make sure NUM LOCK is enabled before attempting this.)
  
Table language drivers

Paradox comes equipped with a variety of table language drivers. By specifying a driver, you control how your table is sorted and which character set is used. For more information, see Table language drivers.

Notes

  For more information about these issues and concepts, consult your Windows documentation.
  
  These issues are of particular interest to those working in international environments, but they apply to all users.
  
Character set issues

Because Paradox is a Windows application, it supports the ANSI character set for files that can be used only by other Windows applications. This includes forms, reports, scripts, and libraries. Paradox stores OEM characters in tables. This means Paradox translates ANSI characters to those in your OEM code page when saving table data.

For example, if you are using code page 437 (the default code page for U.S. workstations that support ASCII) and place an "" (ANSI character 198) in a field, Paradox saves it as OEM character 146. You will see the same character when viewing the table, but it is not literally the same one you originally entered.

Most of the time, this is transparent; that is, there is no loss of data. However, if you enter a character that is not supported by your code page, Paradox converts it to one that is. For example, if you are using code page 437 and type an "", Paradox converts it to an "O" because your code page does not support the original character. In this example, a mild form of data loss occurs; the tilde ( ~ ) is removed.

If you enter an ANSI character that cannot be converted to a similar character in your code page, Paradox replaces it with OEM character 254 (().

Character conversion occurs when you

  Enter data into a table
  
  Name a file
  
  Export data to OEM files or applications
  
In all other operations, Paradox uses and saves characters from the ANSI character set.

Sorting conventions

Paradox uses language drivers to sort tables according to different conventions. If you are using a workstation with non-U.S. settings or are working with tables created on non-U.S. workstations, make sure Paradox is using the language driver(s) closest to the conventions you are used to. For information on language drivers, see Table language drivers.

In most cases, you should not have to worry about a table's language drivers after setting the default drivers for your workstation. When sharing tables between workstations, make sure the workstations are using the same default language drivers.

Data formats

In Paradox, the default symbols and formats used for your data are based on the regional settings in the Windows Control Panel. For example, if you set your Windows Control Panel money symbol to "$", Paradox uses it when displaying money values. Similarly, Paradox formats date and time values according to the settings used by Windows.

To set the Paradox defaults permanently to different formats, begin by altering the settings in the Windows Control Panel. When you alter these settings it affects the default formats used in all Paradox operations, except some internal data conversion operations.

Internal data conversion

Many operations require Paradox to convert a string of characters to a number, date, or time value. For example, when you enter a date into a table, Paradox converts the characters you type to a value representing a date. This process is automatic and generally uses format settings in the Windows Control Panel to control the conversion. However, a few operations use the BDE to convert character strings to number, date, or time values and to convert these data formats to character strings. These operations include

  queries that use selection criteria or perform pattern matching on number and date fields
  
  table restructures that change alpha fields to number or date fields (and the reverse)
  
  adding or subtracting records between tables that do not have the same structure
  
Because these operations use the BDE for this internal data conversion, you must ensure the BDE configuration file uses the same data format conventions and settings as the Windows Control Panel; otherwise, unexpected results might occur.

In most cases, you will not have to worry about these settings, because the BDE (when installed) is configured to the data format conventions of the country defined in the Windows Control Panel. However, if you customize the Windows Control Panel so it uses settings that are different from your country's data format conventions, you should also configure the BDE to the same settings; otherwise, queries that match date and numeric values may yield unexpected results.

For example, the "forward-slash" (/) is commonly used in U.S. workstations as a date separator. If you change this to an ampersand ( & ) in the Windows Control Panel, you should also configure the BDE so that it uses an ampersand for a date separator.

This does not affect the way data is formatted when you display it. Paradox uses the settings in the Windows Control Panel to display data. Note that the use of standard data formats is recommended wherever possible.

To configure the BDE to specialized date, time, or number formats

1.	Click Start, Paradox, Utilities, Database Engine to start the BDE Administrator.

2.	Click the Configuration page.

3.	Double-click the System icon and then double click the Formats icon.

4.	Click one of the Date, Time, or Number icon.

You will probably need to change the formats in all three sections.

5.	On the right panel, type the parameters in the various format sections that match those of the new data format.

For information on the specific sections of the format pages, see the BDE Administrator online Help.

You can also update the BDE to the current settings in the Windows Control Panel by reinstalling the BDE.

Notes

  Make a backup of the BDE configuration file before changing it with the BDE Administrator.
  
  If you customize the BDE so it uses special number formats, you may not be able to share saved queries with other workstations unless those workstations have also been customized to the same settings.
  
Tip

  If you want a special format for a specific table or field, change the appropriate Format properties.
  
Preventing unsupported character conversion

If you want to prevent Paradox from converting characters that are unsupported by the code page, you can use the Strict Translation command while editing a table. If you turn Strict Translation on and try to save a record containing characters that are not supported by your code page, Paradox displays the message "Character(s) not supported by Table Language" and prevents you from saving the record until you do one of the following:

  Remove (or replace) the unsupported characters.
  
  Turn off Strict Translation.
  
To turn Strict Translation on or off

  Click Format, Strict Translation.
  
A check mark indicates that the option is enabled.

Table language drivers

A table's language driver determines the table's sort order (based on the order of the letters in the alphabet) and available character set. You can choose a default language driver for Paradox and dBASE tables from the BDE Configuration Utility.

Paradox uses table language drivers to:

  open any Paradox table with the correct language driver. This includes opening tables with different language drivers in the same Paradox session.
  
  open dBASE tables with the correct language driver
  
  create tables generated by copy operations using the language driver of the copied table
  
  create tables generated by import operations with the default language driver of the file format (Paradox or dBASE)
  
  determine the language driver of a query's Answer table using the language driver of the first (topmost) query image in the query
  
Changing the default language driver

To change the Paradox default language drivers, run the BDE Configuration Utility. Each language driver is appropriate only for a particular code page; for example, the Paradox International (Paradox 'intl') driver works with code page 437 only. Use language drivers appropriate for your code page. To see the language drivers appropriate for each code page, see the BDE Configuration Utility Online Help. You can assign different language drivers to different tables

To open the BDE Configuration Utility

  Click Start, Paradox, Utilities, Database Engine.
  
To change the default language driver

1.	In the BDE Administrator, click the Configuration page.

2.	Double-click Drivers on the left panel.

3.	Double-click Native and click Paradox.

4.	Click Langdriver on the right panel.

5.	Choose a language driver from the list box.

Changing a table language driver

If you need to change the table language of an existing table that contains data, you must first duplicate the table's structure with the language driver you want, then append the original table's data to the new table.

Caution

  If you change the language driver of a table that contains data, you risk losing special characters in the table.
  
To duplicate a table's structure

1.	Click File, New, Table.

2.	Click the Blank button.

3.	Choose the appropriate table type from the list box and click OK.

4.	Click Borrow.

5.	Select the table whose structure you want to borrow and enable all of the options you want to borrow (usually this is all options).

6.	Click Open.

7.	Follow steps 2 to 4 of the next procedure.

The new table uses the language driver you specified, and all its structure information (such as field names) is in the format of that language driver.

To change the default table language driver

1.	With a table open, click Format, Restructure Table.

2.	Choose Table Language from the Table Properties list box.

3.	Click Modify.

4.	Choose a language driver from the Language list box and click OK.

This procedure is recommended only for newly-created tables (as above).

To append the original table's data to the new table

1.	Click Tools, Utilities, Add.

2.	Double-click the original table.

3.	Select the new table.

4.	Enable the Append button in the Options section.

5.	Click Add.

Paradox appends the data to the new table in transliterated format, as specified by the new language driver.

Note

  To enter a euro dollar currency symbol into your table data, you need to change the language driver of you table to ascii ANSI. Ensure that you have Euro Currency support for Windows installed on your system. The ascii ANSI code for the euro dollar currency symbol is ALT + 0128.
  
Working with tables using different language drivers

Although you can use different language drivers for different Paradox tables, linking tables using different language drivers is not advised. This includes (but is not limited to) operations such as the following:

  Joining tables using different language drivers in queries.
  
  Adding or subtracting two tables based on different language drivers.
  
  Creating multi-table documents based on tables with different language drivers.
  
  Defining referential integrity between tables based on different language drivers.
  
  Defining a lookup table using a table based on a language driver different than the master table.
  
Paradox is designed to handle such operations; however some language driver combinations may yield unexpected results. For best results, choose one language driver, then restructure your tables so they use that driver.

Note

  You can use Paradox language drivers only for Paradox tables.
  
File extensions for Paradox objects

The following table lists the types of files (objects) generated by Paradox, and their extensions.

Extension	Type of object

.CFG	Configuration file

.DB	Paradox table

.DBF	dBASE table

.DBT	Memos for a dBASE table

.DM	Saved data model

.FAM	Paradox listing of related files (like a table's .TV file)

.FDL	Delivered form

.FP	Form or report printer style sheet

.FSL	Saved form

.FT	Form or report screen style sheet

.FTL	Temporary file created then deleted when you save a form

.INI	Configuration file

.LCK	Lock file

.LDL	Delivered library

.LSL	Saved library

.LTL	Temporary file created then deleted when you save a library

.MB	Memos for a Paradox table

.MDX	Maintained index of a dBASE table

.NDX	Nonmaintained index of a dBASE table

.PX	Primary index of a Paradox table

.QBE	Saved query

.RDL	Delivered report

.RSL	Saved report

.RTL	Temporary file created then deleted when you save a report

.SDL	Delivered script

.SQL	Saved SQL file

.SSL	Saved script

.STL	Temporary file created then deleted when you save a script

.TV	Table view settings for a Paradox table

.TVF	Table view settings for a dBASE table

.TVS	Table view setting for SQL data

.VAL	Validity checks and referential integrity for a Paradox table

.Xnn	Secondary single-field index for a Paradox table, numbered

.Ynn	Secondary single-field index for a Paradox table, numbered

.XGn	Composite secondary index for a Paradox table

.YGn	Composite secondary index for a Paradox table

Paradox field names and types

Choosing a field name is a very important factor in table design. Follow the following rules when specifying field names for Paradox tables.

Paradox field naming rules

  The maximum length of a field name is 25 characters.
  
  A field name cannot start with a blank space (unless it is enclosed in quotation marks), but it can contain blank spaces.
  
  Each field name in a table must be unique. (You cannot have two identical field names.) You cannot make a name unique by adding a blank space at the end of the name or changing the capitalization of the name.
  
  Paradox does not allow you to use extended characters as field names.
  
  If you plan to use the table with ObjectPAL,a field name should not contain the following characters:
  
Square brackets [ ], curly braces { }, or parentheses ( )

The combination of a dash and a greater-than symbol ->

Periods (.), underscores (_), or pipes (|)

The # symbol by itself (you can combine # with other characters, as in the field name Phone #)

  If you plan to use the table in a query, a field name should not contain commas (,), pipes (|), or exclamation points (!) because these characters have special significance. 
  
  Avoid using SQL keywords such as SELECT and COUNT.
  
Field types and sizes chart

Paradox provides a cataloge of field types and their corresponding sizes. You can access this list by right-clicking on Field Type. Here is a list of the valid Paradox field types and sizes:

Type	Size	Symbol

Alpha	1 - 255	A

Number		N

Money		$

Short		S

Long Integer		I

BCD	0 - 32*	#

Date		D

Time		T

Timestamp		@

Memo	1 - 240**	M

Formatted Memo	0 - 240**	F

Graphic	0 - 240***	G

OLE	0 - 240***	O

Logical		L

Autoincrement		+

Binary	0 - 240***	B

Bytes	1 - 255	Y

* Number of digits after the decimal point

** Memo and formatted memo fields can be virtually any length. The value you specify in the Create Table dialog box refers to the amount of the memo Paradox stores in the table (1 to 240 characters for memos and 0 to 240 characters for formatted memos). The entire memo is stored outside the table. For example, if you assign a size value of 45 to the field, Paradox stores the first 45 characters in the table. It stores the whole memo field in another file (with the extension .MB) and retrieves it as you scroll through the records of the table.

*** Optional

Tips

  If all your memos are smaller than a given size (for example, 200 characters), you can save space and time by setting the memo field size equal to or larger than this size. Paradox stores the entire memo in the table if it is less than the given size.
  
  If you are hooked up to a network, you can insert a hyperlink in a field. Simply define an alpha field and specify its size as 255. In your table, type the web site address. The type should change color when you move off the field. You can access the web ite immediately if you click on the field while in View mode.
  
Field types used by Paradox

The following field types are used by Paradox. Any field you create in a Paradox table must be defined as one of these types.

  Alpha fields
  
  Number fields
  
  Money fields
  
  Short fields
  
  Long integer fields
  
  BCD fields
  
  Date fields
  
  Time fields
  
  Timestamp fields
  
  Memo fields
  
  Formatted memo fields
  
  Graphic fields
  
  OLE fields
  
  Logical fields
  
  Autoincrement fields
  
  Binary fields
  
  Bytes fields
  
Compatible Paradox field types

When converting a Paradox field from one type to another, use the following chart to determine field type compatibility.



Convert to:	A	N	$	D	S	M	F	B	G	O	L	I	T	@	#	+	Y

A	Y	P	P	P	P	Y					P	P	P	P	P		Y

N	Y	Y	Y		P						Y	Y			Y	<	

$	Y	Y	Y		Y						Y	Y			Y		

D	Y			Y										Y			

S	Y	Y	Y		Y						Y	Y			Y	<	

M	Y					Y	Y	Y									

F						Y	Y	Y									

B								Y									

G								Y	Y								

O								Y		Y							

L	Y	Y	Y		Y						Y	Y			Y	<	

I	Y	Y	Y		Y						Y	Y			Y		

T	Y												Y	Y			

@	Y			Y									Y	Y			

#	Y	Y	Y		Y						Y	Y			Y		

+	Y	Y	Y		Y						Y	Y			Y	Y	

Y	Y																Y

Y:	Paradox allows the conversion, but may trim data. If Paradox must trim data, you will see the Restructure Warning dialog box, which asks you to confirm the conversion.

Blank:	The field type conversion is not allowed.

P:	The conversion is allowed, but might generate the Problems table.

<:	Conversion to autoincrement is allowed only from a single-field key containing data that is <2147483647

Paradox field types allowing arithmetic operators

This table shows which arithmetic operators can be used in each Paradox field type.



Operator	A	N	$	S	I	#	D	T	@	M	F	G	O	L	+	B	Y

+	Y	Y	Y	Y	Y	Y	Y	Y	Y								

-		Y	Y	Y	Y	Y	Y	Y	Y								

*		Y	Y	Y	Y	Y		Y	Y								

/		Y	Y	Y	Y	Y		Y	Y								

( )	Y	Y	Y	Y	Y	Y	Y	Y	Y								

+ means addition

- means subtraction

* means multiplication

/ means division

( ) means brackets (order of operations)

Paradox field types allowing QBE summary operators

Certain types of Paradox fields cannot be queried using summary operators. The following table outlines the types of summary operators supported by each field type.

Operator	A	N	$	S	I	#	D	T	@	M	F	G	O	L	+	B	Y

AVERAGE		Y	Y	Y	Y	Y	Y	Y	Y						Y		

COUNT	Y	Y	Y	Y	Y	Y	Y	Y	Y					Y	Y		Y

MAX	Y	Y	Y	Y	Y	Y	Y	Y	Y					Y	Y		Y

MIN	Y	Y	Y	Y	Y	Y	Y	Y	Y					Y	Y		Y

SUM		Y	Y	Y	Y	Y									Y		

ALL*	Y	Y	Y	Y	Y	Y	Y	Y	Y					Y	Y		Y

UNIQUE*	Y	Y	Y	Y	Y	Y	Y	Y	Y					Y	Y		Y

* By default, SUM and AVERAGE operate on all values in a field; whereas COUNT, MAX, and MIN operate only on unique values. You can override these default groupings by adding the word ALL or UNIQUE to a CALC statement.

Paradox alpha fields

Paradox alpha fields contain strings consisting of

  Letters
  
  Numbers
  
  Special symbols like %, &, #, or =
  
  Other printable ASCII characters. You will use the alpha field type for fields such as name, address (which contains letters and numbers) and phone number. Remember that alpha field types cannot be used in calculations. Use the number field type for data that may need to be manipulated.
  
Paradox number fields

Paradox number fields must contain only numbers. Number fields can hold positive or negative values. The range of values possible for a number field is from -10e307 to 10e308 with 15 significant digits. Use number fields when you plan to perform calculations on the values in the fields.

Tip

  It is a good idea to use an alpha field rather than a number field for phone numbers or zip codes. In an alpha field, you can include parentheses and hyphens.
  
Paradox money fields

Paradox money fields, like number fields, can contain only numbers. They can hold positive or negative values. But by default, money fields are formatted to display decimal places and a money symbol. Regardless of the number of decimal places displayed, Paradox recognizes up to six decimal places when performing internal calculations on money fields.

Paradox short fields

Paradox short fields are special number fields that can contain only whole numbers in the range -32,767 to 32,767. Short fields require less disk storage than ordinary number fields. They are available only in Paradox tables.

Because they do not allow the same formatting options as number fields, short fields should be used only by advanced Paradox users.

Paradox long integer fields

Paradox long integer fields are 32-bit signed integers that contain whole numbers (nonfractional) with complete accuracy in the range -2147483648 to 2147483647 (plus or minus 2 to the 31st). Long integer fields require more space to store than short fields.

Paradox BCD fields

Paradox BCD fields contain numeric data in a BCD (Binary Coded Decimal) format. Use BCD fields when you want to perform calculations with a higher level of precision than that available with the use of other numeric fields. Calculations on BCD fields are not performed as quickly as those on other numeric fields.

The BCD field type is provided primarily for compatibility with other applications that use BCD data. Paradox correctly interprets BCD data from other applications that use the BCD type. However, when Paradox performs calculations on BCD data, it converts the data to the numeric float type, then converts the result back to BCD.

Note

Although BCD fields can handle larger numbers, you can only enter a number with 15 or fewer significant digits into a BCD field.

Paradox date fields

Paradox date fields can contain any valid date from January 1, 9999 BC to December 31, AD 9999. Paradox correctly handles leap years and leap centuries and checks all dates for validity. Paradox treats all BC years as leap years.

Paradox provides three date formats:

  Windows Short uses the short date format you define from the Windows Control Panel International dialog box.
  
  Windows Long uses the long date format you define from the Windows Control Panel International dialog box.
  
  mm/dd/yy displays dates using two-digit numbers for the month, followed by the day, followed by the year, each separated by a slash mark (/).
  
  DB Date displays dates using one digit for months and days 1 through 9 and two digits for the year in the format month/day/year (for example, 1/1/01).
  
  ISO Date displays a four-digit year followed by two-digit numbers for the day and month, each separated by periods, in the format year/month/day (for example, 1901.01.01).
  
You can also define your own custom format.

Paradox time fields

Paradox time fields contain times of day, stored in milliseconds since midnight, and are limited to 24 hours.

Paradox provides two formats for entering and displaying time variables.

  Windows Time uses the time format you define in the Windows Control Panel International dialog box.
  
  hh:mm:ss am Formats the time to display two digits of hours, minutes, and seconds, separated by colons and followed by AM or PM.
  
You can also define your own custom format.

Paradox timestamp fields

Paradox timestamp fields contain both time and date values. To enter today's date and the current time, press SPACEBAR repeatedly until Paradox enters the data. Rules for this field type are the same as those for date fields and time fields.

Paradox memo fields

Use memo fields for text strings that are too long to store in an alpha field.

Memo fields can be virtually any length. The size value you assign refers to the amount of the memo Paradox stores in the table. This can be from 1 to 240 characters. Paradox stores the whole memo outside the table (in the .MB file). Paradox retrieves the data from the .MB file as you scroll through the records of the table. The amount of data a memo field contains is limited only by the disk space available on your system.

Memo fields can contain letters, numbers, special symbols (such as %, &, #, and =), or any other printable ASCII character (except null). You can enter line breaks, tabs, and other print control characters in memo fields.

You can display memo data in table view; however, only a portion will appear in this limited space. If you click View, Memo View, you can view your memo data in full.

Tip

  If all your memos are smaller than a given size (for example, 200 characters), you can save space and time by setting the memo field size to be equal to or larger than this given size. You will still have an .MB file, but Paradox will not have to access it to display the field's data.
  
Paradox formatted memo fields

Use memo fields for text strings that are too long to store in an alpha field. Formatted memo fields are exactly the same as memo fields except that you can format font, style, color, and size of the text.

Formatted memo fields can be virtually any length. The size value you assign refers to the amount of the memo Paradox stores in the table. This can be from 1 to 240 characters. Paradox stores the whole memo outside the table (in the .MB file). Paradox retrieves the data from the .MB file as you scroll through the records of the table. The amount of data a memo field contains is limited only by the disk space available on your system.

Memo fields can contain letters, numbers, special symbols (such as %, &, #, and =), or any other printable ASCII character (except null). You can enter line breaks, tabs, and other print control characters in memo fields.

You can display formatted memo data in table view; however, only a portion will appear in this limited space. If you click View, Memo View, you can view your formatted memo data in full.

Tip

  If all your memos are smaller than a given size (for example, 200 characters), you can save space and time by setting the memo field size to be equal to or larger than this given size. You will still have an .MB file, but Paradox will not have to access it to display the field's data.
  
Paradox graphic fields

Paradox graphic fields contain pictures. You can create graphics in a painting or drawing application, or scan in images. Paradox supports the following image file formats: .BMP, .PCX, .TIF, .GIF, .EPS, and .JPG.

When you paste a graphic into a graphic field, Paradox converts the graphic into the .BMP format.

Graphic fields do not require a size because they are not stored in the table, but in separate files.

Note

  Paradox does not support 32-bit graphics.
  
Paradox OLE fields

Use the OLE field to store different kinds of data such as images, sound, documents, and so on. The OLE field provides you with a way to view and manipulate this data without leaving Paradox.

You do not need to specify a size for OLE fields because they are not stored in the table, but in separate files.

Paradox logical fields

Paradox logical fields contain values representing true or false (yes or no). By default, valid entries include "True" and "False" (case is not important).

You can format the text of Paradox logical fields.

Paradox autoincrement fields

Paradox autoincrement fields contain long integer, read-only (non-editable) values. Paradox begins with the number 1 and adds one number for each record in the table.

Deleting a record does not change the field values of other records.

When creating a Paradox table, you can specify the starting number of an autoincrement field by specifying a minimum value for it.

Paradox binary fields

Binary fields should be used only by Paradox application developers and advanced users who need to work with data that Paradox cannot interpret. Paradox cannot display or interpret binary fields, but ObjectPAL can access them. A common use of a binary field is to store sound.

Unlike bytes fields, binary fields do not require a size because they are stored in a separate file (the .MB file), not in the table.

Paradox bytes fields

Bytes fields should be used only by Paradox application developers and advanced users who need to work with data that Paradox cannot interpret. Paradox cannot display or interpret bytes fields, but ObjectPAL can access them. A common use of a bytes field is to store bar codes or magnetic strips.

Unlike binary fields, bytes fields are stored in the Paradox table (rather than in the .MB file), allowing for faster access.

Compatibility with other applications

You can open a Paradox table in any ODBC-compliant application and share data between various database applications using the Paradox ODBC driver. You can also open a table from any ODBC-compliant application in Paradox. Listed below are the applications that are compatible with Paradox. Click on any application type to study the conventions each uses for field names, types, and sizes.

  dBASE tables
  
  DB2 field names, types, and sizes
  
  Informix field names, types, and sizes
  
  InterBase field names, types, and sizes
  
  Microsoft Access field names, types, and sizes
  
  Microsoft SQL Server field names, types, and sizes
  
  Oracle field names, types, and sizes
  
  Sybase field names, types, and sizes
  
dBASE tables

You can use Paradox to open, create, or restructure dBASE tables. You can also easily copy dBASE tables into Paradox and vice-versa. If you prefer to work with dBASE, there are certain procedures you will need to know to perform tasks such as creating indexes, maintained indexes, and expression indexes.

dBase field names, types, and sizes

In order to create a dBASE table with Paradox, you must follow certain guidelines for defining field names, types, and sizes.

Names

Follow these rules when specifying field names for dBASE tables (unless you are creating dBASE 7 tables):

  A field name cannot exceed 10 characters (up to 31 characters in dBASE 7).
  
  A field name cannot contain blank spaces.
  
Each field name in a table must be unique. You cannot have two identical field names. You cannot make a name unique by adding a blank space at the end of the name or changing the capitalization of the name.

Types and sizes

The valid dBASE field types and sizes are



Symbol	Size	Decimal Point	Type

C	1 - 254		Character (alpha)

F*	1 - 20	0 - 18, and <=Size - 2	Float (numeric)

N	1 - 20**	0 - 18, and <= Size - 2	Number (BCD)

D	8		Date

L	1		Logical

M***	NA		Memo

O****	NA		OLE

B****	NA		Binary

l*****	NA		Long Integer

@*****	17		TimeStamp

%*****	8		Double

+*****	4		Autoincrement

*Available only in dBASE IV and later versions.

** For dBASE III+ tables, the size can be from 1 - 19.

***Memo field formats differ between dBASE III+ and later versions of dBASE.

****Available only in dBASE for Windows and later versions.

*****Available only in dBASE 7.

dBASE character fields

dBASE character fields can contain any printable character (including blank spaces). The maximum size of a dBASE character field is 254.

dBASE float fields

dBASE provides two ways to store numeric data. The float number type contains numeric data in a binary floating-point format. Use the float number type on fields that will not require precise calculations to be performed on them; some degree of precision is rounded or truncated during calculation. Float number fields are best used to contain whole numbers, or numbers of up to two decimal places.

The size of a dBASE float number field can be from 1 to 20.

Setting decimal places

You set the number of decimal places in the Dec column of the Field Roster in the Create/Restructure dialog box.

In the Dec column, you specify how many decimal places to store. Enter a number at least 2 less than the field size. This is because Paradox counts the decimal point and sign (if any) as part of the field size.

dBASE number fields

dBASE number fields contain numeric data in a Binary Coded Decimal (BCD) format. Use number fields when you will need to perform precise calculations on the field data. Calculations on number fields are performed more slowly, but with greater precision than on float number fields.

The size of a dBASE number field can be from 1 to 20 (except for dBASE III+ tables, which can be from 1 to 19).

Setting decimal places

Set the number of decimal places in the Dec column of the Field Roster in the Create/Restructure dialog box.

In the Dec column, you can specify how many decimal places to store. Enter a number at least 2 less than the field size. This is because Paradox counts the decimal point and sign (if any) as part of the field size.

dBASE date fields

Date fields contain dates. The default date entry and display format is Windows Short (which uses the short date format you defined in the Windows Control Panel International dialog box), but you can format dBASE date fields the same way you format Paradox date fields.

The size for a date field is always 8.

dBASE logical fields

Logical fields contain a single character representing True or False (Yes or No) values. In dBASE logical fields, logical true can be entered as T, t, Y, or y. Logical false can be entered as F, f, N, or n. The size for a dBASE logical field is always 1.

dBASE logical fields have the Logical Format choice on their menu. Choose it to choose what values to accept in the logical field. You will see a menu of your most recent formats (such as True/False or Male/Female).

dBASE memo fields

dBASE memo fields contain blocks of text that are too large to be stored in a character field. The contents of memo fields are stored externally to the table. You do not specify a field size for dBASE memo fields.

dBASE OLE fields

Use the OLE field to store different kinds of data, such as images, sound, documents, and so on. The OLE field provides you with a way to view and manipulate this data without leaving Paradox. You do not need to specify a size for OLE fields because they are not stored in the table, but in separate files.

dBASE binary fields

Binary fields should be used only by application developers and advanced users who need to work with data that Paradox cannot interpret. Paradox cannot display or interpret binary fields, but ObjectPAL can access them. A common use of a binary field is to store sound. Binary fields do not require a size because they are stored in a separate file (the .DBT file), not in the table.

dBASE Long Integer fields

Long Integer fields allow you to store more space than short fields but only up to 4 digits (whole numbers).

dBASE TimeStamp fields

A dBASE Timestamp field contains both a date format (MM/DD/YY) and time format (HH:MM:SS). 

dBASE Double fields

A dBASE Double field has a default/maximun size of 8 digits (whole numbers), allowing you to store more accurate numeric values.

dBASE Autoincrement fields

dBASE Autoincrement fields contain long integer values in a read-only (non-editable) field, beginning with 1 and automaticlaly incrementing. Deleting a row does not change the field values of other rows.

dBASE record lock fields

In a multiuser environment, each user can place record locks on a shared table. For example, if user JSMITH is editing record number 12 of Stock, user MBROWN cannot access that record until it is unlocked. This prohibits one user from unintentionally overwriting another user's work.

The dBASE table type gives you the Record Lock option to show you information about a locked record. If you check Record Lock, Paradox adds a hidden field to the table. This field shows you when a record was locked and by whom.

Use the Create dBASE Table dialog box to create the Record Lock field for a dBASE table. Record Lock is not available for dBASE III+ tables.

The information you see when you find a locked field depends on the Info Size you specify. The Record Lock field can be from 8 to 24 characters. The default is 16.

  The first two characters tell whether a user has changed the record.
  
  The next three characters tell the time a user placed the lock.
  
  The next three characters tell the date a user placed the lock.
  
  The remaining 16 characters are optional. They tell the name of the user that placed the lock.
  
The default size of 16 displays the changed status of the record, the time and date of the lock, and the first 8 characters of the user who placed the lock.

Note

  Although Paradox adds the Record Lock field to the table, you will not see it when you view the table. You see a record's Record Lock field only if you are locked out of that record.
  
dBASE field types allowing arithmetic operators

This table shows which arithmetic operators can be used in each dBASE field type.

Operator	C	F	N	D	L	M	O	B

+	Y	Y	Y	Y				 

-		Y	Y	Y				

*		Y	Y					

/		Y	Y		 			

( )		Y	Y	Y				

dBASE field types allowing summary operators

Operator	C	F	N	D	L	M	O	B

AVERAGE		Y	Y					 

COUNT	Y	Y	Y	Y	Y			

MAX	Y	Y	Y	Y	Y			

MIN	Y	Y	Y	Y	Y			

SUM		Y	Y		 			

ALL*	Y	Y	Y	Y	Y			

UNIQUE*	Y	Y	Y	Y	Y			

* By default, SUM and AVERAGE operate on all values in a field; whereas COUNT, MAX, and MIN operate only on unique values. You can override these default groupings by adding the word ALL or UNIQUE to a CALC statement.

Compatible dBASE field types

You restructure a dBASE table the same way you do a Paradox table. Changing field types of dBASE fields has different consequences for each field type.

Number to character

Data in number fields or float number fields can be converted to text in a character field with no loss of data. However, you cannot perform calculations on numeric data stored in a character field.

Character to number or float number

You can convert a character field to a number or float number field with the following results:

  If the data in the character field is numeric (digits), Paradox converts it to a number or float number field with no data loss.
  
  If the data in the character field is a mixture of text and digits beginning with digits, Paradox converts the digits to a number or float number format and deletes all text.
  
  If the data in the character field is a mixture of text and digits beginning with text, Paradox assigns the value 0 to the number or float number field.
  
Logical to character

Logical values are converted to T or F text values.

Logical to number or float

True values are converted to 1 and False values are converted to 0.

Character to logical

The characters T, t, Y, and y are converted to logical true, and all other values are converted to logical false.

Date to character

You can convert a date value to a text value. The text value will be eight characters in the format MM/DD/YY.

Character to date

You can convert a text value to a date value only if it is an eight-character value in the format MM/DD/YY. Any other value sizes or formats are not recognized as dates and are not converted.

Memo to character

Values that are longer than the size of the character field are trimmed.

dBASE tables and indexes

When working with dBASE tables, Paradox uses an index to organize the records in a table according to the values in one or more fields.

When you create an index on a dBASE table, Paradox creates a file that contains the indexed field's values and their corresponding record numbers. Paradox refers to the index file when locating and displaying the records in a table.

When you use an index on a dBASE table, the records appear in a different order. However, the records remain stored in the same physical location in which you originally entered them.

Although Paradox supports both .MDX files and .NDX files, it is recommended that you use a dBASE production index (the .MDX file which uses the table name as its file name) whenever possible. Although you can create nonproduction .MDX files as well as .NDX files, Paradox automatically maintains only the production index.

Creating an index on a dBASE table

When you create an index on a dBASE table, you can either create it based on a field or an expression. You can also create a subset condition expression (also called a filter), which is an expression that evaluates to true or false. Paradox creates an index for a dBASE table that points only to values that meet the filter's requirements. For example, if you create the subset condition expression State=CA, you tell Paradox to create an index on those values in the State field that match the value CA.

To define a field or group of fields as an index

1.	Open a table.

2. Click Format, Restructure Table.

3.	Click the Secondary Index tab.

4.	Click Add and type a name to define a new Secondary Index.

5.	In the Fields box, select the field or fields on which you want to define the secondary index.

6.	Click the right arrow to move the field into the Selected Index Fields box.

7.	Enable any of the following check boxes:

  Maintained-Paradox automatically updates the index whenever you update the table. A table must have a key before you can create a maintained secondary index.
  
  Unique-(you must first enable Maintained before you can enable Unique) determines whether records can have duplicate values in the secondary index field or fields. If two or more records have the same value in the secondary index field, the attempt to define the secondary index fails. You have to eliminate duplicate values before defining the secondary index.
  
  Descending-alphebetically sorts the index in descending order
  
To define an index based on an expression

1.	Open a table.

2. Click Format, Restructure Table.

3.	Click the Secondary Index tab.

4.	Click Add and type a name to define a new Secondary Index.

5.	Enable the Expression Index button to create an index based on an expression

6.	Do one of the following:

  In the Expression Index box, type an expression. You can type any formula that results in a value. For example, you could create an expression index such as FIRST_NAME + LAST_NAME, where FIRST_NAME and LAST_NAME are field names.
  
  In the Subset Condition (filter) expression box, type an expression that evaluates to true or false. 
  
7.	Enable any of the following check boxes:

  Maintained-Paradox automatically updates the index whenever you update the table. A table must have a key before you can create a maintained secondary index.
  
  Unique-(you must first enable Maintained before you can enable Unique) determines whether records can have duplicate values in the secondary index field or fields. If two or more records have the same value in the secondary index field, the attempt to define the secondary index fails. You have to eliminate duplicate values before defining the secondary index.
  
  Descending-alphebetically sorts the index in descending order.
  
Note

  You can use the =, <=, and >= comparison operators in expression indexes; =< and => are not supported. See your dBASE documentation for syntax.
  
Functions in expression indexes on dBASE tables

The following dBASE IV functions are supported. See your dBASE documentation for syntax.

ABS	DTOR	LOG10	RTRIM

ACOS	DTOS	LOWER	SIGN

ASC	DTOS	LTRIM	SIN

ASIN	EXP	MAX	SPACE

AT	FIXED	MIN	SQRT

ATAN	FLOAT	MOD	STR

ATN2	FLOOR	MONTH	STUFF

CEILING	FV	PAYMENT	SUBSTR

CHR	IIF	PI	TAN

COS	INT	PV	TRANSFORM

CTOD	ISALPHA	RAT	TRIM

DAY	ISLOWER	RAND	UPPER

DIFFERENCE	ISUPPER	REPLICATE	VAL

DIV	LEFT	RIGHT	YEAR

DOW	LEN	ROUND	

DTOC	LOG	RTOD	

Viewing indexed dBASE tables in a different order

You can use the Filter Table command to sort an indexed dBASE table based on any of the secondary indexes you have defined for the table. When you change the view order of a dBASE table, the record numbers (which show the true location of each record in the table) are shown out of order.

To view indexed dBASE tables using a production index

1.	Open a table, form, or report.

2.	Click Format, Filter.

3.	In the Filter Tables dialog box, enable the Order By check box.

The list box below the Order By check box shows all tags included in the table's production index (the .MDX file that shares the table name).

4.	Click an index from the list below the Order By check box. If you want records to appear in natural order, choose NO INDEX.

To view indexed dBASE tables using an index other than the production index

You can use a different index (an .NDX file or a tag from a different .MDX file).

1.	Open a table, form, or report.

2.	Click Format, Filter.

3.	Type the name of the index (including its .MDX or .NDX extension) in the dBASE Index File field.

Note

  To specify a descending as opposed to an ascending view order, or a case-insensitive as opposed to a case-sensitive view order, you must first define the index you use to the specifications you want.
  
Maintained dBASE indexes

You tell Paradox to automatically maintain a dBASE index when you define an index on the Secondary Index tab of the Create or Restructure dialog box. When you check the Maintained option, Paradox updates the index every time the table changes. This speeds up certain operations like queries.

  Paradox saves a maintained index as part of an .MDX file and gives the .MDX file the same name as the table. This is your production index. It is recommended that you use production indexes when working in Paradox.
  
  When you save a maintained index, Paradox asks you for a tag name. The .MDX file can contain several maintained index specifications.
  
  Maintained is unavailable for dBASE III+ tables.
  
  Nonmaintained indexes are assigned the .NDX file extension. You cannot have a production .NDX file.
  
  You must use the Filter Table command (open the table and click Format, Filter) to open a nonmaintained index each time before you edit data in the table. Otherwise the non-maintained index will become unsynchronized with the table, and thus unusable.
  
You cannot restructure a nonmaintained index.

Creating a maintained index for a dBASE III Plus table

You will be warned when you save the table that the driver level will change to dBASE IV. Maintained indexes were introduced in dBASE I; therefore, the table level must be changed to save the new index. This means that your dBASE table cannot be opened in dBASE III PLUS, and that it will generate an error message saying "Corrupt table/index header" in all versions that predate dBASE IV.

Note

  For more information on creating or restructuring a dBASE table, see "Creating an index on a dBASE table."
  
dBASE linking combinations

You can link dBASE tables

  only on like field types, unless you use an expression index in the link
  
  only on maintained indexes (not .NDX files)
  
You can link dBASE tables using an expression index or a single-field index in an .MDX file. The following table shows valid dBASE links.

From	To

Field	Expression index

Field	Single-field index

Master Expression	Expression index

Master Expression	Single-field index

Limitations on reports containing dBASE tables

There are a few limitations on reports whose data models contain dBASE tables. The limitations apply if a report's master table is linked in a single-value relationship with a dBASE table. (Paradox creates this kind of link if the detail table contains a unique index.) For such a report, you cannot

  sort the report's record band (you cannot right-click it and choose Sort)
  
  add a group band to the report
  
To avoid these limitations, restructure the detail table with a nonunique index and recreate the data model for the report and link the tables in a multi-value relationship.

Paradox and dBASE field type compatibility

In an Add operation, the rules for adding records from one type to another are the same as those for restructuring from one table type to another.

You can add records from one table type to another only if the tables have a compatible structure. This means compatible field types in the same order. The following table shows which Paradox and dBASE field types are compatible.

	dBASE C	dBASE F	dBASE N	dBASE D	dBASE L	dBASE M	dBASE O	dBASE B

Paradox								

A	Yes	P	P	P	P	Yes	No	No

N	Yes	Yes	Yes	No	P	No	No	No

$	Yes	Yes	Yes	No	No	No	No	No

D	Yes	No	No	Yes	No	No	No	No

S	Yes	Yes	Yes	No	P	No	No	No

M	No	No	No	No	No	Yes	No	Yes

F	No	No	No	No	No	Yes	No	Yes

B	No	No	No	No	No	Yes	No	Yes

G	No	No	No	No	No	Yes	No	Yes

O	No	No	No	No	No	Yes*	Yes	Yes

I	Yes	Yes	Yes	No	Yes	No	No	No

#	Yes	Yes	Yes	No	Yes	No	No	No

T	Yes	No	No	Yes	No	No	No	No

@	Yes	No	No	Yes	No	No	No	No

L	Yes	Yes	Yes	No	Yes	No	No	No

+	Yes	Yes	Yes	No	Yes	No	No	No

Y	P	No	No	No	No	Yes	No	No

Yes	The field types are compatible.

No	The field types are not compatible.

P	The field types are somewhat compatible, but conversion can result in a Problems table.

*	You can add from a Paradox OLE field to a dBASE IV memo field, but not to a dBASE memo field.

When you add data from a Paradox formatted memo to a dBASE memo, Paradox removes all formatting and converts the data to straight text.

When you add data from a Paradox graphic, OLE, or binary field to a dBASE memo, the dBASE table can accept the data, but cannot display it.

The table you add the records to can have more fields than the source table, as long as the first fields of the table you add the records to are compatible with all fields of the source (compatible field types in the same order). Paradox places null values in the extra fields.

Copying from Paradox to dBASE tables

Paradox automatically changes field types when you change table types. The following table shows what to expect when you copy from a Paradox table to a dBASE table.

From Paradox type	To dBASE type	Side effects

Alpha	Character	

Number	Number	Assigns size (20) and dec. (4)

Money	Number	Assigns size (20) and dec. (4)

Short 	Number	Assigns size (6) and dec. (0)

Long Integer	Number	Assigns size (11) and dec. (0)

BCD	Number	Assigns size (20) and dec. (4)

Date	Date	

Time	Character	Assigns size (8)

Timestamp	Character	Assigns size (30)

Memo	Memo	

Formatted memo	Memo	Formatting is lost

Graphic	Binary 	

OLE	OLE	

Logical	Logical	

Autoincrement	Number	Assigns size (11) and dec. (0)

Binary	Memo	Data cannot be displayed

Bytes	Memo	Data cannot be displayed

If the new dBASE table contains no production index (.MDX file), no float number field type, and no memo field type, Paradox creates a dBASE III+ table. If the dBASE table contains an OLE or binary field, Paradox creates a dBASE for Windows table. Otherwise, Paradox creates a dBASE IV table.

If in the Borland Database Administrator, the Level parameter for the dBASE driver is set to 4 instead of 5, graphic and OLE Paradox fields convert to dBASE memo fields. Bytes fields cannot be converted.

You can copy a Paradox table to a dBASE table, or a dBASE table to a Paradox table, by typing the file extension you want (.DB for Paradox and .DBF for dBASE) for the copied table. For example, if you want to copy the Paradox Customer table to a dBASE Customer table, type CUSTOMER.DBF as the name of the copied table.

If the new dBASE table contains no production index (.MDX file), no float number field type, and no memo field type, Paradox creates a dBASE III+ table. If the dBASE table contains an OLE or binary field, Paradox creates a dBASE for Windows table. Otherwise, Paradox creates a dBASE IV table.

Paradox automatically changes field types when you change table types.

Copying from dBASE to Paradox tables

Paradox automatically changes field types when you change table types. The following table shows what to expect when you copy from a dBASE table to a Paradox table.

From dBASE type	To Paradox type	Side effects

Character	Alpha	

Float 	Number	Removes size

Number	Number	Removes size

Logical	Logical	

Date	Date	

Memo	Memo	Adds size (1)*

OLE	OLE	

Binary	Graphic 	

* Paradox assumes the data in the dBASE memo is in text form. If the memo contains a different type of data, you should use the Add utility and add the memo to the appropriate Paradox BLOB field type.

You can copy a Paradox table to a dBASE table, or a dBASE table to a Paradox table, by typing the file extension you want (.DB for Paradox and .DBF for dBASE) for the copied table. For example, if you want to copy the Paradox Customer table to a dBASE Customer table, type CUSTOMER.DBF as the name of the copied table.

If the new dBASE table contains no production index (.MDX file), no float number field type, and no memo field type, Paradox creates a dBASE III+ table. If the dBASE table contains an OLE or binary field, Paradox creates a dBASE for Windows table. Otherwise, Paradox creates a dBASE IV table.

Paradox automatically changes field types when you change table types.

DB2 field names, types, and sizes

Rules for DB2 field names, types, and sizes

There are two types of identifiers: ordinary identifiers and delimited identifiers. 

An ordinary identifier:

  Must start with a letter
  
  Can include uppercase letters, numbers, and underscores
  
  Lowercase letters are stored as uppercase letters
  
A delimited identifier:

  Must be enclosed within double quotation marks
  
  Can include uppercase and lowercase letters, numbers, underscores, and spaces
  
  Can contain a double quotation mark, represented by two consecutive double quotation marks
  
Leading spaces are stored as part of a delimited identifier, but trailing spaces are ignored.

DB2 field names, types, and sizes

The following table is a list of valid DB2 field types and sizes. For detailed information on field types and sizes, see your DB2 documentation.

Name	Description

VARCHAR	Variable-length character data with a maximum of 4000 characters.

CHAR	Fixed-length character data

DECIMAL	For a decimal number.

NUMERIC	

SMALLINT	For a small integer.

INTEGER	For a large integer.

REAL	

FLOAT	For a floating point number.

DOUBLE	For a floating point number.

LONG VARBINARY	

DATE	For a date.

TIME	For a time.

TIMESTAMP	For a timestamp.

CLOB	For a character large object string.

BLOB	For a binary large objects string.

DBCLOB	For a double-byte character large object string.

Informix field names, types, and sizes

Rules for Informix field names

  The maximum length of a field name is 18 characters.
  
  A field name must begin with a letter (A-Z, a-z).
  
  A field name can contain digits from 0 to 9, uppercase or lowercase letters, and underscore (_) characters.
  
  Each field name in a table must be unique. (You cannot have two identical field names.)
  
Informix field types and sizes

The following table list, valid Informix field types and sizes. For detailed information on field types and sizes, see your Informix documentation.

Name	Size	Dec	Description

CHAR	1-32,769		Fixed-length character data

SMALLINT			Whole number -32,767 to +32,767

INTEGER			Integer -2,147,483,647 to +2,147,483,647

SMALLFLOAT			Single-precision floating-point number with approximately 8 significant digits

FLOAT			Single-precision floating-point number with up to 16 significant digits

MONEY	0-32	0-32	Fixed-point number with up to 32 significant digits

DECIMAL	0-32	0-32	Decimal floating-point number with up to 32 significant digits

DATE			Calendar date Jan 1, 1900 to Dec 31, 9999

DATETIME			Calendar date Jan 1, 0001 to Dec 31, 9999 and 24-hour time of day

INTERVAL			Span of time (year-month or day-time)

SERIAL			Sequential number up to 2,147,483,647 assigned automatically by the database server when a row is inserted

BYTE			Any type of binary data

TEXT			Variable-length character data to 2,147,483,647 bytes

VARCHAR	1-255		Variable-length character data

Note

  In Paradox you can create all Informix field types, and you can view and edit data in all fields except BYTE, CHAR > 255, and TEXT.
  
InterBase field names, types, and sizes

Rules for InterBase field names

  The maximum length of a field name is 31 characters.
  
  A field name must begin with a letter (A-Z, a-z).
  
  A field name can contain letters (A-Z, a-z), digits, $, or underscore (_) characters.
  
  You cannot use InterBase reserved words for table names. See the InterBase Programmer's Reference for a list of reserved words.
  
  Each field name in a table must be unique. (You cannot have two identical field names.)
  
Interbase field types and sizes

The following table lists valid InterBase field types and sizes. For detailed information on field types and sizes, see your InterBase documentation.

Name	Size	Dec	Description

SHORT			Integer -32,768 to +32,767

LONG			Integer -2,147,483,647 to +2,147,483,647

FLOAT			Floating-point number with up to 7 digits of precision

DOUBLE			Floating-point number with up to15 digits of precision

CHAR	0-32,767		Fixed-length character data

VARCHAR	0-32,767		Variable-length character data

DATE			Calendar date Jan 1, 0100 to Dec 11, 5941

BLOB			Any type of binary data

ARRAY			You cannot create an ARRAY field

Note

  In Paradox you can create all InterBase field types except ARRAY, and you can view and edit data in all fields except BLOB.
  
Microsoft Access field names, types, and sizes

Rules for Microsoft Access field names, types, and sizes

  Names can be 64 characters long
  
  Any combination of letters, numbers, space, special characters except (.), an exclamation point (!), accent grave (') and brackets ([]).
  
Microsoft Access field types and sizes

The following table lists of valid Microsoft Access field types and sizes. For detailed information on field types and sizes, see your Microsoft Access documentation.

Name	Size	Dec	Description

CHAR	255		Fixed length character data.

VARCHAR			Variable-length character data

DATETIME			Date and time values for the years 100 through 9999

BIT			

MONEY		1-4	Stores currency values and numeric data 15 digits to the left and 4 digits to the right

SHORT			Integer -32,768 to 32,767

LONG			Integer -2,147,483,648 to 2,147,483,647

DOUBLE		15	Stores from-1.79769313486232E308 to-4.444065645841247E-324 and 1.79769313486232E308 to 4.44065645841247E-324 15 points of precision

LONG TEXT	1-255		

LONG BINARY			

AUTOINCREMENT	1		Field values incremented by 1.

BYTE	0-255		Stores numbers from 1-255 (no fractions)

FLOAT			Stores floating-point number with 15 points of precision

BINARY	1-255		Fixed-length binary data up to 255 bytes

Note

  Paradox can open, edit, and create Microsoft Access tables if Microsoft Access or the Jetengine .DLLs are installed on you system.
  
Opening a Microsoft Access table

In order to launch or create a Microsoft Access table, you must change the settings in the Borland Database Engine (BDE).

To launch the BDE

  Click Start, Program Files, WordPerfect Office, Utilities, Borland Database Engine.
  
To change settings in the BDE

1.	In the BDE Administrator, click Object, New.

2.	Select MSACCESS from the Database Driver Name list box, and click OK.

3.	On the Definition tab, click on the Database name and enter a path for the Access table.

4.	On the toolbar, click the blue right arrow to apply your changes and click OK to confirm the changes.

5.	On the Configuration tab, click the plus sign to the left of Configuration, click the plus sign to the left of Drivers, click the plus sign to the left of Native, and select MSACCESS from the list of drivers.

6.	On the Definition tab, select DLL32 and from the list box to the right, select IDDA3532.DLL.

If you are opening an older Access table (version 1, 2, or 95), select IDDAO32.DLL.

7.	Select DATABASE NAME, and enter the full path of your MSACCESS database name or click the browse button to find the file.

8.	On the toolbar, click the blue right arrow to apply your changes.

9.	Click File, Close to close the BDE.

You can now open MSaccess tables in paradox using the MSAccess alias you just created.

Note

  For more information on opening Microsoft Access tables, see the BDE online help. 
  
  A Microsoft Access table cannot be created or saved unless there is already an existing Microsoft Access Database on your system (indicated as an alias).
  
Microsoft SQL Server field names, types, and sizes

Microsoft SQL Server types and sizes

The following table is a list of valid field types and sizes. For detailed information on field types and sizes, see your Microsoft SQL Server documentation.

Name	Size	Description

CHAR	255	Fixed-length character data

VARCHAR	255	Variable-length character data

INT	10	

SMALLINT	5	

TINYINT	3	

FLOAT	6	Floating-point number with up to 6 digits of precision

MONEY	19	

TEXT	2147483647	Variable-length character data up to 19

BINARY	255	Fixed-length binary up to 255

VARBINARY	255	Variable-length binary up to 255

IMAGE	2147483647	Variable length binary data up to 2,147,483,647

BIT	1	Either 0 or 1. Cannot be NULL. Integer values other than 0 or 1 are interpreted as 1

DATETIME	23	

TIMESTAMP	8	

REAL	7	

SMALL MONEY	10	

SMALL DATETIME	16	

DECIMAL	28	Supports a maximum precision of 28 digits

NUMERIC	28	Supports a maximum precision of 28 digits



Oracle field names, types, and sizes

Rules for Oracle field names

  The maximum length of a field name is 30 characters.
  
  A field name must begin with a letter (A-Z, a-z).
  
  A field name can contain letters (A-Z, a-z), digits (0-9), or the _, $, or # characters.
  
  You cannot use ORACLE reserved words for remote table names, quoted table names, or quoted index names. For a list of reserved words and other naming restrictions, see the ORACLE Programmer's Reference.
  
  Each field name in a table must be unique. (You cannot have two identical field names.)
  
Oracle field types and sizes

The following table lists valid Oracle field types and sizes. For detailed information on field types and sizes, see your Oracle documentation.

Name	Size	Description

CHAR	1-255	Fixed-length character data

RAW	1-255	Binary data to 255 bytes

DATE		Calendar date Jan 1, 4712 BC to Dec 31, AD 4712 and 24-hour time of day

NUMBER	0-38	Floating-point number with up to 38 digits of precision

LONG		Variable-length character strings up to 2 gigabytes ((2**32)-1 bytes)

LONG RAW		Binary data up to 2 gigabytes

FLOAT		Floating-point number with up to 38 digits of precision

VARCHAR2	1-2000	Variable-length character data

VARCHAR	1-255	Variable-length character data

REFCURSOR		

Note

  In Paradox you can create all Oracle field types, and you can view and edit data in all fields except LONG, LONG RAW, and RAW.
  
Sybase field names. types, and sizes

Rules for Sybase field names

  The maximum length of a field name is 30 characters.
  
  A field name must begin with a letter (A-Z, a-z).
  
  A field name can contain letters (A-Z, a-z), digits (0-9), or the _, $, or # characters.
  
  You cannot use SQL Server reserved words for remote table and column names. See the SQL Server Programmer's Reference for a list of reserved words.
  
  Field names may be case sensitive, depending on how SQL Server is installed.
  
  Each field name in a table must be unique. (You cannot have two identical field names).
  
Sybase field types and sizes

The following table lists valid Sybase field types and sizes. For detailed information on field types and sizes, see your Sybase documentation.

Name	Size	Description

CHAR	1-255	Fixed-length character data

VARCHAR	1-255	Variable-length character data

DECIMAL		

NUMERIC		

INT		Integer -2,147,483,647 to +2,147,483,647

SMALLINT		Integer -32,768 to +32,767

TINYINT		Integer 0 to 255

FLOAT		8-byte floating-point number

MONEY		-922,337,203,685,477.5808 to +922,337,203,685,477.5808

TEXT		Variable-length character data up to 2,147,483,647 bytes

BINARY	1-255	Fixed-length binary data up to 255 bytes

VARBINARY	1-255	Variable-length binary data up to 255 bytes

IMAGE		Variable-length binary data 0 to 2,147,483,647 bytes

BIT		Either 0 or 1. Cannot be NULL. Integer values other than 0 or 1 are interpreted as 1

DATETIME		Calendar date Jan 1, 1753 to Dec 31, 9999 and 24-hour time of day

TIMESTAMP		Binary timestamp

REAL		4-byte floating-point number

SMALLMONEY		-214,748.3648 to +214,748.3647

SMALLDATETIME		Calendar date Jan 1, 1900 to Jun 6, 2079 and 24-hour time of day

Note

  In Paradox you can create all Sybase field types, and you can view and edit data in all fields except BINARY, IMAGE, TEXT, TIMESTAMP, and VARBINARY.
  





