Aloha upgrade question

[AkamaiAloha]

Hi all,

I've seen my share of goofy little issues when upgrading the Aloha POS, but there is one I never quite understood.

When you upgrade, I noticed that on certain systems, there are issues handling the "old" Aloha dated subdirectories from way back when. Generally, the result is that you want view the old sales data, and but you can't because it says the data base needs to be upgrade (and I assume the data needs to be reground). Sales data created AFTER the upgrade is usually fine. However, trying to regrind the old subdirectories using the regrind utility or from the command line usually results in a error message saying that the data needs to be upgrade.

I don't see this on every upgrade... I assume it has something to do with how far ahead you many versions you "skip" (i.e. going from 4.2 right to 5.3, which I am not even sure you're technically supposed to do).

Anyway, what is the "official" way to handle the old data to make it viewable again when you're faced with this situation.

Thanks in advance!

 

[RadAlohaQE]

use the /forceconvertlog flag at the end of the grind or grindq command on the old dated subs.

 

[ezcrane]

using the regrind subdirectory utility in aloha manager will automatically run a dbup on the dated sub if need be before attempting to regrind

 

[AkamaiAloha]

I haven't tried Rad's suggestion yet, but I did try using the regrind utility prior to posting that, and had the same problem. It would tell me the db needed to upgraded, and that was it. Always possible I could have a made a mistake--not sure how, as simple as that utility is--but who the hell knows.