No change because dbforms do not know anything about the new inserted value - remember it must'nt be maximum of the number.
I handle this problem by not using autoInc - i just use the preInsert interceptor to add retrieve a new key index from the database
and insert this into the resultset. Then dbforms knows the new index an can jump to the new record.
If you do not select the MAX index (to put after that record), how do you retrieve a new key index?
Oh by the way, interceptors are not thread safe are they? So if you have many users making inserts then it would be possible that someone could get an error saying 'duplicate key for record whatever'.
Of course if I could get redisplayFieldsOnError to work I wouldn't have to worry about this so much ;^)
--
Shawn
Happily using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/
------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _______________________________________________ DbForms Mailing List
http://www.wap-force.net/dbforms
