Cary A Marshall wrote:

> We've recently upgraded a third party payroll package on our
> development machine. This required setting up new tables which are
> included in a single Image dataset. We're getting ready to run the
> upgrade again ( for practice before upgrading our production machine)
> on the developmnent machine, but we would like to avoid re-doing all
> the table entries again. And those same tables will be used on the
> production machine as well. So here's my question:  What's the best
> way of storing/restoring that dataset?

Thou shalt not store/restore individual datasets.

You might check around for DB2DISK/DISK2DB or some equivalent programs
that have circulated around in the contributed software library for
ages, or if you don't have the CSL, you might find it on one of the
3000-friendly web sites or ftp directories.  With these programs you can
export image datasets to flat files and vice versa, although the usual
Image restrictions exist (load masters before details, etc).  These
programs use straightforward Image intrinsics to do their work, so you
have to play by the rules.

Adager may have a built-in to do this.

Jeff Kell <[log in to unmask]>