Since 29/March/2013, GN3Export exports from object libraries also the objects with the linked images.

In order for that to work, on the computer where GN3Export runs, the drive with the high-resolution pictures (typically on the OPI server) must be mapped with the same drive name as on the OPI server.

An example

On the OPI server, the pictures are in E:\OPI\HIGH\....

On the computer where GN3Export runs, you must map to the E: drive letter the root of the E: drive of the OPI server, e.g:

net use e: \\opiservername\e$

If the drive name is already busy

If the GN3Export runs on the GN3 database server, and the required drive name is already busy, you can attempt to perform the export on the OPI server itself.

In order to this to work, the OPI server must have in the registry the GN3 key. Using regedit, export the GN3 key from the registry of the database server, and then copy the exported file to the OPI server and run it to load it in the registry.

Copy the folder with all the GN3Export files on the OPI server and perform the export with a similar syntax as below (assuming that the libraries belong to the title with id=13):

C:\gn3-2-gn4\Gn3Export.exe -target 1.4 -title 13 -node lib -out libs.xml

Should you want to test the export only on one library, assuming that the libraries belong to the title with id=13 and that the library id is 1234, use this syntax:

C:\gn3-2-gn4\Gn3Export.exe -target 1.4 -title 13 -node lib:ID=1234 -out libs.xml