> -----Original Message-----
> From: Kundl, Eric [mailto:[log in to unmask]]

> We are just trying to make sure that all our databases that 
> are supposed to have identical structure actually do.
> 
> An Adager schema and compare works, but if a couple items are in
> different order, it throws the rest of the compare pretty much out of
> wack (or whack).

Then, by definition, these databases are "not the same" [even though they may contain the same elements, "a different order" could have catestrophic results if you use image list "@;" -- everything -IN SCHEMA ORDER-]

(though I'll admit that having, say, the PASSWORDS part in a different order may not be a cause for concern; and in most cases even the ITEMS part won't hurt you because very few people use the "numeric" image item lists, i.e., specifying everything by their internal item number...)

And, having said that, A different order of datasets *may* be of concern as well, but only if you reference sets-by-number -OR- expect to map sets to real MPE filenames on a consistent basis.

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *