13/13

# Index

A B C D E F H I J L M N O P Q R S T U V

## A

  advanced server features, 2.2
  application startup performance, 5.3

## B

  building a mapping query, B.2

## C

  CASCADE UPDATE referential integrity constraints, B.5
  CASCADE UPDATE trigger code, B.5
  change default data types, 3.3
  client/server, 2.2
  column validation, B.4
  Config, 5.2

## D

  Data Access Objects, 2.1
  database users in the Oracle Model, 2.2.5
  declarative default values, B.3
  declarative referential integrity, 2.1.3
  default data type mappings, 3.3
  drivers
    ODBC, 5.1
  drop-down lists, 5.5.3
  dynaset, 2.1.1
  dynasets and primary keys, 2.3

## E

  emulation of COUNTER data type, B.1
  errors
    modifying Microsoft Access database, 4.6
  explicit transaction model, 2.1.5
  extending, application, 2.6

## F

  field names
    length considerations, 2.4.1
    spaces replaced by underscores, 2.4.1
  FORCE option
    used to create views, 3.5

## H

  hard lock, 2.1.2

## I

  implicit transaction model, 2.2.4

## J

  Jet, 2.1
  Jet data types, 3.2
  Jet error message classes, A.1
  Jet error messages, A.2
  Jet multi-user updates, 2.1.2
  Jet recordsets, 2.1.1
  Jet transactions, 2.1.5

## L

  large-scale application, 5.1

## M

  Microsoft Access data types, 3.2
  migration process, 2
  modify Microsoft Access database
    errors, 4.6
  MSysConf table, 5.2
  multi-user Microsoft Access application, 2.1

## N

  nValue, 5.2

## O

  ODBC, 2.2.4
  ODBC drivers, 5.1
  OMWB_EMULATION user, 2.2.5
  one-to-many cardinality, 2.1.3, B.5
  one-to-one cardinality, 2.1.3, B.5
  optimistic locking, 2.1.2
  Oracle architecture, 2.2
  Oracle data types, 3.1
  Oracle reserved words, 3.4

## P

  parameter table, 5.2
  performance of ODBC drivers, 5.1
  performance of snapshots and dynasets, 5.5.2
  pessimistic locking, 2.1.2
  pivot tables
    migration of TRANSFORM statements, 3.6
  PL/SQL, 2.2.2
  preparing for migration, 2.4
  primary keys and dynasets, 2.3

## Q

  qualified queries, 5.5.1
  queries
    conversion to Oracle views, 3.5

## R

  reduce network traffic, 5.5.1
  referential integrity, 2.1.3
  relations with queries, 4.2
  removing Microsoft Access security, 4.1
  reserved word conflicts, 3.4
  restricted queries, 5.5.1
  result sets, large, 5.5.2
  result sets, small, 5.5.2

## S

  security, removing Microsoft Access, 4.1
  sequence, 2.2.3
  sequence, definition, B.1
  single-user Microsoft Access application, 2.1
  snapshot, 2.1.1
  stored procedures, 2.2.1
  supported Oracle data types, 3.1

## T

  table names
    length considerations, 2.4.1
    spaces replaced by underscores, 2.4.1
  table validation, B.4
  transactions, 2.1.5
  TRANSFORM statements for pivot tables
    migrating, 3.6
  triggers, 2.2.1
  tuning, 5

## U

  users
    in the Oracle Model, 2.2.5

## V

  views
    migration of Microsoft Access queries, 3.5
    need to recompile or rebuild without FORCE option, 3.5