lupins46 is pretty much correct in what he says with the exception of the installation difficulties.
I develop and distribute Access programs myself and have used both the Office XP developer and the newer Access 2003 Developer Extensions. If you set the install path to, let's say "C:\Programms\MYProgramm\" then your program should let itself install on all machines without any problem. Only drawback that I can think of is with older versions of the Windows installer.
I haven't used the XP developer for a while, but I think I'm right in saying that the user can also select where he/she wants the program installed (with 2003 Dev. this is the case). The program will then be installed in the chosen directory with all libraries and files.
Where you might encounter difficulties is with macro security. Any program that has macros and or Visual Basic code that is to be opened with Office 2002 will result in warnings about macro security that the user first has to answer before the program starts. This can be combated in that you update all machines with the newest JET Database and MDAC (both available on the MS download page). Depending on your network security you may have to digitally sign your program.
If your program is intended to be multi user then consider creating a client/server database (front end – backend). In the front end you will place your forms, queries, reports etc., the back end holds the tables for your database. Initially you can create just one db with all objects, once you're happy with the design simply export your tables into a new db and place this db on your server. By using the table linking assistant you can link your front end to the back end. One more point, you must set the front end db to share in the options dialog. The front end db is the one that you will distribute.
Have a look at the Microsoft Knowledge Base for the developer and multi user db's, you should find enough information to help you in your decisions.
hth
