Skip to content

Saving records, type not found error

Forums Forums SIMPOL Programming Saving records, type not found error

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #243
    Dan Jinks
    Participant

    I am copying a subset of records from an sbme table to a vola1table, using db1util.sma->copy_db1rec_to_db1table db1util.sma->copy_db1rec_to_db1trec In copy_db1rec_to_db1table, on the statement: r.save(error=iErrnum) with the following error: Error (18): Type not found Error: a statement of function “vola1indexprivate.find” was executed unsuccessfully I then copied the above db1util.sma functions and modified then to use vola1table, vola1record, vola1field type variables for the destination objects. The result was the same error, no other errors. I have exclusive lock on the target table and shared lock on the vola1base object. I commit the vola1base after each record is saved. The error occurs on the SECOND record I try to save, not the first. Since I cannot debug into the save function, I’m not sure how to proceed. Could someone provide advice on what to try next? I will convert everything to abme1 file and try again. At least I can then review the first record in Personal, which might reveal more information. -Dan

    #1891
    Michael
    Keymaster

    On 18/07/2011 21:42, djinks wrote:
    > I am copying a subset of records from an sbme table to a vola1table,
    > using db1util.sma->copy_db1rec_to_db1table
    > db1util.sma->copy_db1rec_to_db1trec
    >
    > In copy_db1rec_to_db1table, on the statement: r.save(error=iErrnum)
    >
    > with the following error: Error (18): Type not found Error: a
    > statement of function "vola1indexprivate.find" was executed
    > unsuccessfully
    >
    > I then copied the above db1util.sma functions and modified then to
    > use vola1table, vola1record, vola1field type variables for the
    > destination objects. The result was the same error, no other
    > errors.
    >
    > I have exclusive lock on the target table and shared lock on the
    > vola1base object. I commit the vola1base after each record is saved.
    > The error occurs on the SECOND record I try to save, not the first.
    > Since I cannot debug into the save function, I'm not sure how to
    > proceed. Could someone provide advice on what to try next?
    >
    > I will convert everything to abme1 file and try again. At least I
    > can then review the first record in Personal, which might reveal
    > more information.

    Dan,

    can you send me an example that is reproducible? I will open it up with
    the vola1base source and have a look. The vola1base source is fairly
    old, and it may be that I missed something or that things have somehow
    changed in an incompatible way in one of the libraries.

    Ciao, Neil

    #1894
    Dan Jinks
    Participant

    I'll try to create a example app tomorrow.
    -Dan

    On 7/18/2011 5:20 PM, Neil Robinson wrote:
    > On 18/07/2011 21:42, djinks wrote:
    >> I am copying a subset of records from an sbme table to a vola1table,
    >> using db1util.sma->copy_db1rec_to_db1table
    >> db1util.sma->copy_db1rec_to_db1trec
    >>
    >> In copy_db1rec_to_db1table, on the statement: r.save(error=iErrnum)
    >>
    >> with the following error: Error (18): Type not found Error: a
    >> statement of function "vola1indexprivate.find" was executed
    >> unsuccessfully
    >>
    >> I then copied the above db1util.sma functions and modified then to
    >> use vola1table, vola1record, vola1field type variables for the
    >> destination objects. The result was the same error, no other
    >> errors.
    >>
    >> I have exclusive lock on the target table and shared lock on the
    >> vola1base object. I commit the vola1base after each record is saved.
    >> The error occurs on the SECOND record I try to save, not the first.
    >> Since I cannot debug into the save function, I'm not sure how to
    >> proceed. Could someone provide advice on what to try next?
    >>
    >> I will convert everything to abme1 file and try again. At least I
    >> can then review the first record in Personal, which might reveal
    >> more information.
    >
    > Dan,
    >
    > can you send me an example that is reproducible? I will open it up with
    > the vola1base source and have a look. The vola1base source is fairly
    > old, and it may be that I missed something or that things have somehow
    > changed in an incompatible way in one of the libraries.
    >
    > Ciao, Neil
    >

    #1895
    Dan Jinks
    Participant

    I sent you the project last night via email.
    -Dan

    On 7/18/2011 5:20 PM, Neil Robinson wrote:
    > On 18/07/2011 21:42, djinks wrote:
    >> I am copying a subset of records from an sbme table to a vola1table,
    >> using db1util.sma->copy_db1rec_to_db1table
    >> db1util.sma->copy_db1rec_to_db1trec
    >>
    >> In copy_db1rec_to_db1table, on the statement: r.save(error=iErrnum)
    >>
    >> with the following error: Error (18): Type not found Error: a
    >> statement of function "vola1indexprivate.find" was executed
    >> unsuccessfully
    >>
    >> I then copied the above db1util.sma functions and modified then to
    >> use vola1table, vola1record, vola1field type variables for the
    >> destination objects. The result was the same error, no other
    >> errors.
    >>
    >> I have exclusive lock on the target table and shared lock on the
    >> vola1base object. I commit the vola1base after each record is saved.
    >> The error occurs on the SECOND record I try to save, not the first.
    >> Since I cannot debug into the save function, I'm not sure how to
    >> proceed. Could someone provide advice on what to try next?
    >>
    >> I will convert everything to abme1 file and try again. At least I
    >> can then review the first record in Personal, which might reveal
    >> more information.
    >
    > Dan,
    >
    > can you send me an example that is reproducible? I will open it up with
    > the vola1base source and have a look. The vola1base source is fairly
    > old, and it may be that I missed something or that things have somehow
    > changed in an incompatible way in one of the libraries.
    >
    > Ciao, Neil
    >

Viewing 4 posts - 1 through 4 (of 4 total)
  • You must be logged in to reply to this topic.