Simple questions - compiling etc

[john]

First in earlier docs Ive seen there is no compiler . is there a
compiler for Access ? Is it a compiler like I assume a compiler should
be like say Clipper for xbase code? You know standalone exe file etc?


Ive also read something about an ADT file or something to distribute
it if you have a developers package.

Also is the whole package related to a database called ---- a
database? Im used to thinking of a database being the same as a
table. Are all the indexes, tables and code related to one program
created in an entity called a database?

So if I make a employee database that also has several tables say an
employee and hours worked table - they both are included in a thing
called database by Access? When go save it and all the related code,
forms and indexes its all saved under EMPLOYEE DATABASE in access?

 

[Baz]

First in earlier docs Ive seen there is no compiler . is there a
compiler for Access ? Is it a compiler like I assume a compiler should
be like say Clipper for xbase code? You know standalone exe file etc?


Ive also read something about an ADT file or something to distribute
it if you have a developers package.

Also is the whole package related to a database called ---- a
database? Im used to thinking of a database being the same as a
table. Are all the indexes, tables and code related to one program
created in an entity called a database?

So if I make a employee database that also has several tables say an
employee and hours worked table - they both are included in a thing
called database by Access? When go save it and all the related code,
forms and indexes its all saved under EMPLOYEE DATABASE in access?

Access contains a compiler, but it doesn't produce a standalone EXE file.
The compiled code remains within the Access mdb or adp file. What a
compiler "should" be for you is something only you can decide! I have no
idea what Clipper does.

If you buy the developer's tools, you can then distribute a run-time-only
version of Access which means that end users do not need to have Access.

If you are used to a "database" being the same as a "table", then you need
to change your thinking! Sounds like something you've picked up from clunky
old "database" software that stores each table in it's own ISAM file.

Most sensibly-designed Access applications consist of two files: a front-end
that contains the forms, reports and code, and a back-end that contains the
tables, indexes and so on. You don't have to do it that way - you can put
it all in one file - but it's not a good idea.

Alternatively, instead of the Access front-end linking to an Access
back-end, it can link to any ODBC-compliant data source. Or, it can link
directly to SQL Server by means of an Access Database Project (adp).

IMO, it is not correct to regard Access as a database. It is a Windows
client development technology which is very heavily oriented to database
applications. The choice of database engine is up to you, although the Jet
database engine that is integrated into Access is very good within certain
limitations.