ONLINE 6.0 LOCKING

J> From: jesolom@pbrock.srv.PacBell.COM (Rock Solomon) J> I have a database with logging turned off, because I'm making a lot of chang s > to it, and will turn logging on later. My problem is that I have declared a > cursor that includes all the records in a table, and update particular ones > in the process. What happens is the program eventually fails because the loc > table overflows. Without "logging", how do I "commit" these updates every so > often so this does not occur? One way is to use a foreach and count rows, and after some arbitrary amount, say 1000, do a commit. This does not work in circumstances where you need a full rollback, but does work nicely for large deletes, where if there is a fail, big deal, you can restart deleting where you left off. --- ~ SPEED 1.40 [NR] ~