I think you are trying to confuse a few things, in how it's operating.

The paths have to be Unix accessible from each server. I don't think you can load a set of defs from a directory not on that server, but it might be possible (eg: copy the defs you want to to a defs2 directory, for example).

If you load that table, to $DB2, then anything that $DB2 is used as a handle for will use that other set of defs and tables.

Any operations on that will operate on those tables. Any variables initialized as pointers to those objects will also operate on those tables. You need to grab another data object, $DB to operate on your local tables.

You need to copy any data to $DB if you wanted to save it in your local tables, where $DB was the local defs.

In theory, the .defs should only tell the object where to find the table, how to access it (eg: password) and then how to load it (the defs in the directory).

But, that object will now only operate on that set of tables.


PUGDOG� Enterprises, Inc.

The best way to contact me is to NOT use Email.
Please leave a PM here.