That is good news if the nextval statements weren't broken. I was running into trouble with a few pages that used sequence.nextval. So, I figured out the three or four ways you suggest converting it, and worked out the issues. Then, I greped the system, found 28 pages of nextvals. I refined my list, and came just short of 300 files where nextval was being used in the Oracle fashion--sequence.nextval. So, I just worked through the whole list. I know it fixed my immediate problems.
I'm glad that such a gaping hole wasn't actually left open. However, I know that the whole system hasn't felt nearly as flakey since I worked through this issue. (I used to run into a lot of buggy pages which I would ignore if I were just touring the toolkit, but would hammer through if it was important to me.)
Anyway, thanks for your encouragement and added insight into the issue.