Saving a snapshot of the repository is your best bet.
Technically, the repository consists of a standard Windows folder containing the following:
:arrow: 1) Data base file. This contains all the "administrative"info of your files. Stuff like assosiations and folders. There is only one such file per repository (plus a backup).
:arrow: 2) Binaries. A pretty good bunch of these. These files are the ones containing the actual geometric data for each prt/drw/assy.
:arrow: 3) A single, small file with the name of the repository.
Alibre has a config file where the actual Windows path for any repository is contained. This file is read at startup so AD knows where to look for reps.
Ok, so much for theory. If you wanted to transfer a rep from one machine to other, you could locate the folder, copy it to the other machine (or CD) and then write the path for this new rep into the config file of the AD installation of the new machine.
Creating a Snapshot of a rep is an automatic way to do the above. AD compresses all the files in the rep folder into a single file. When you import it from another AD installation, you will be asked for a Windows location for the folder and AD will automatically uncompress the files to that location and will also automatically update your config file. Pretty cool 8) .
We use this function all the time to transfer stuff to other AD users. The Snapshot will create a *.adb file which can be treated as any Windows file (burned, emailed, ftp'd, network'd). When imported, it will create an identical repository containing all drawings, parts, assemblies, folders, version history, etc. I'm sure it will do the trick :idea:
One last thing. I have a spare repository in my system called "brief case". When I need to transfer something, I just copy the folder(s) to the "brief case" rep and then add the name of the project and the date to the "brief case" name. So the final name is "Brief case (bagger 02) (24-Ag-2004)". This way, when imported on the other system, people are less likely to get confused among different versions and projects they have received. If you ever use a similar technique, after you erase the last folder it contained (from the previous transfer), be sure to empty the recycle bin. I have been emailing huge files composed mainly of undisered data in the recycle bin :wink:
Sorry about the long post, but I suffered badly for this need until the Snapshot thing came along.
Cheers!