>
> If you do not select the MAX index (to put after that
> record), how do you retrieve a new key index?
Depends a little bit of the used database. In Oracle - for example - you can
use a sequence and write a view to get values from the sequence. Most
databases have something like sequence. To be indepent from the database i
define a view in the database to get id - using a sequence.
>
> 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'.
Why should'nt they be not thread safe? I think they must be! It's your own
work to make them thread safe. If you use a sequence in the database the
database makes it thread safe by itselfs.
If you use your max approach you really have this problem...
>
> Of course if I could get redisplayFieldsOnError to work I
> wouldn't have to worry about this so much ;^)
I am heavy at work. Phillip commmented out some lines which deals with
errors and navNew events because he has problems in subforms!
I think here is the problem.
Philip:
Do you remember this change?
// [EMAIL PROTECTED]
// 2003-12-16
// Commented code to fix the following problem:
// Insert invoked in sub-form, validation error, suppose to
re-populate all fields (parent and child)
// Commented code changes all field names to INSERT type -
making repopulate impossible!
Could you construct a bookstore example to reproduce the problem with
subforms? No we have the problem that inserting data in a single form do
work correct...
Regards,
Henner
-------------------------------------------------------
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
