Access 2002 (XP) bloats DB on a /decompile

Install latest version of VBA6. At time of writing, you can find it here.

Got #Name? (#¿Nombre?) inside date/time fields on some workstations

Check out that there are not missing references to components not installed on that workstation. In my case there was a link to Office Web components. After deactiving it, the program ran correctly on the workstations.

Opening and closing forms very slow in Access 2002 (XP)

When using .mdb, deactivate all "Autorrect Names" checkboxes in the General Tab of the Options dialog. Another tip is to disable subdatasheets (datasheets of subforms). Use this code to disable this feature for all of your tables/forms.

Compact / Repair Access Database (.mdb) with backup: Python script

This script compacts (and repairs if required) the database. It makes a backup first, because sometimes Access corrupts the file even more.This script checks for the logged on users before it starts the process. (It does not use the UserRoster accesible form ADO. Instead, it reads the .ldb file, the .mdb database header page and .ldb file locking. It requires Python 2.3 with win32all extension installed, and DAO 3.6. You can find the script here.

Access 2000/XP/2003 database very slow when using front-end/back-end scheme?

It may be that the language (aka CollatingOrder) is different in backend and frontend. Open frontend and in the inmediate code window try:

    ?CurrentDb.CollatingOrder

Do the same with the backend. If they are different you should establish the Collating Order in the Tools | Options menu, General tab: new order. Now compact both. After that, it should run smoothly.