We are having some multi-user issues having changed our system over to use
cursoradapters (native and SQL). The file which controls the next id for
each table is accessed via a cursoradapter. Unfortunately requery on this
file fails if someone else has updated that file and hasn't yet committed
their change i.e. they are in the middle of a BEGIN/END TRANSACTION. Other
than avoiding getting the next id inside a transaction and requerying inside
an endless loop until successful, I can't think of a way round this. I toyed
with autoincrement fields but we have a lot of parent/child tables where we
need to know the parent id for the child records, so I've abandoned that
idea. We also access the data via ODBC in Crystal so again I think there is
a problem with autoincrement fields.
Has anyone got any other suggestions?
Thanks,
Bernie