There was a problem with udtsort.exe. I thought it was a little bit earlier
than this though. We haven't had a problem with indexes in 5.2.
I would suggest making sure you completely delete the indexes and re-create
them rather than just rebuild. That normally solves any problem with them.
You're not doing anything silly like indexing a 'translate' are you?
To run this (or anything else) on a schedule the easiest thing is to use the
OS scheduler (cron, at) to setup a job that will login to UniData and do
whatever you want. Just remember that the process will go through the LOGIN
VOC item so you may need to update it to make sure it doesn't take you
straight into your application.
With more specifics on the OS someone can likely give you a better idea on
exactly what you need to do.
There is also more help available at www.u2ug.org. There are both forums
(not used as much) and a mailing list (quite heavily used).
hth
Colin
Quote:
I am running version 5.2 of UniData. I have an ERP package that
operates on a dozen core tables with indexes. These indexes sometimes
go bad and cause reporting issues. Is there a way to automatically
rebuild indexes on a schedule, so I can once a week rebuild all the
indexes on my system? |