Subject | Re: [IBO] (unknown) |
---|---|
Author | Helen Borrie |
Post date | 2004-05-01T23:46:41Z |
At 06:59 PM 1/05/2004 -0300, you wrote:
you simply use the standard way to acquire a new generator value for a
dataset?
In the editable dataset, assuming that --
The primary key column name is TB001_CODIGO_POSICAO
and
The generator name is GENERATOR_POSICAO
This is *all* you need:
In the dataset that needs the value, set the GeneratorLinks property as
follows:
TB001_CODIGO_POSICAO=GENERATOR_POSICAO
Then, as soon as the dataset goes into dssInsert, IBO will fetch the next
generator value and place it into the dataset field
'TB001_CODIGO_POSICAO'. You do not need to do anything further, like
converting to string (????) or comparing with other values or assigning
it. A new generator value is *always* unique and GeneratorLinks will
always assign it where and when it needs to be assigned.
Your code makes my head spin.
Helen
>Dear Dmitry.Without going into your horrendously complicated code, may I suggest that
>
>I tried to do like this, just inserting the code for Tb001_codigo_posicao,
>but when it tries to commit, the error appears again.
>I'm becoming crazy.
you simply use the standard way to acquire a new generator value for a
dataset?
In the editable dataset, assuming that --
The primary key column name is TB001_CODIGO_POSICAO
and
The generator name is GENERATOR_POSICAO
This is *all* you need:
In the dataset that needs the value, set the GeneratorLinks property as
follows:
TB001_CODIGO_POSICAO=GENERATOR_POSICAO
Then, as soon as the dataset goes into dssInsert, IBO will fetch the next
generator value and place it into the dataset field
'TB001_CODIGO_POSICAO'. You do not need to do anything further, like
converting to string (????) or comparing with other values or assigning
it. A new generator value is *always* unique and GeneratorLinks will
always assign it where and when it needs to be assigned.
Your code makes my head spin.
Helen