To be more specific:

- Data modifications without COMMIT or ROLLBACK in jobs, will cause data inconsistency

Transactions can be controlled in Access as with VB

- Performance problems, because they will use the client PC and Access to make loops in the tables and modify data... rather than using stored procedures, etc..

Like any client server technology this can be true. Even in Oracle Forms. If they want to use DB packages they can using ADO.

- Timeout problems with ODBC driver ?

Not noticed this on our apps.

- Cannot use PL/SQL within Access

True, but you can call stored packages/procedures/functions

- SQL standard differs from Oracle to Access ?

Access uses ANSI joins rather than old-style WHERE clause joins. In this respect it is more up to date than Oracle8i. Oracle9i has introduced ANSI joins. You would do well to get used to them. I'm sure in the next few years the old WHERE clause join will be a legacy issue

I've not seen any issues except when Oracle guys are looking at ANSI joins and don't understand them.

Suggestions:

- Use views alot to hide complexities from Access.
- Make sure developers use DB procs/funcs/packages when complex coding is needed.
- Chill out. it's not as bad as it sounds.

Good luck!