My own recent experience of Access isn't that good. The Windows software we develop at work normally uses a Sybase or Oracle database, but in order to distribute evaluation systems without having to worry about licencing issues, I recently had to convert a system over to use Access, in addition to Sybase. The main problem was that differences seemed to exist even in the Access version by itself, depending on whether the Access database was accessed via the JetEngine or ODBC. In fact, I found I had to use the JetEngine in order to specify any referential integrity constraints at all. Access also seems to implement security features in a slightly non standard way, by means of a workgroup information file, that can be a pain to maintain if the database needs to be password protected. Anyway, to cut a long story short, I found Access to be quite noddy compared to Sybase or Oracle, although it does have its uses. For example, it's handy that Access itself doesn't actually have to be present on the machine, so an Access database and Windows application can be distributed to potential clients, and should work so long as the relevant version of the JetEngine has been installed with Windows. For live systems though, we'll be sticking with Sybase.
[ 03-03-2003: Message edited by: RodUK ]</p>