× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



My point must have been missed

I don't think so, but to be clear... the restore (as in RSTxxx command),
did keep the correct identity. If you restored the file and did nothing
more, all would be good in the world, if you created 1000 orders before
the save, the next order after the restore would be 1001, correct? Se
we're agreed, the "restore" works as it should.

The problem lay in the APYJRNCHG command. I see your point, the apply
changes the "data" in the table, but it doesn't change the table itself.
Since the next number is an attribute of the table, and not a row in it,
the apply doesn't change the next-number attribute. It's roughly the
same as if we were complaining that we did a save, then changed the
object description (text) on the object, did a restore and an apply
journal changes and our text wasn't updated as part of the apply, right?
I see your point.

However... an identity column is part of the data, not the object,
regardless of how it's actually implemented. If I apply changes that
result in ids being used that were assigned by an identity then I would
expect the identity to be altered appropriately as part of the restore.
Just 2 different views of it I guess, and as you say, it's a DCR. :)

-Walden

--
Walden H Leverich III
Tech Software
(516) 627-3800 x3051
WaldenL@xxxxxxxxxxxxxxx
http://www.TechSoftInc.com

Quiquid latine dictum sit altum viditur.
(Whatever is said in Latin seems profound.)


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.