Database Problem

[hsegars]

I purchased the upgrade from Imatch 2021 to 2023 a few days ago. I ran a database check on my database in Imatch 2021 and it finished with no errors. I then made a copy of the database as well as the Imatch 2021 folder and installed Imatch 2023 and updated the database. After it ran a database check, it found 101 errors. I rechecked the copy of the database in Imatch 2021 and it completed with no errors. I uninstalled Imatch 2023 and reinstalled it and tried to update the database and still had the 101 errors. I ran the database check a number of times with no resolution.I attached a copy of the diagnosis log. Thanks for your help.

[Mario]

I have never seen this error message returned from the database system.
But IMatch 2023 ships with an updated version of the database system, so this might be a new "check" during their diagnosis...?
No other user reported a similar problem.

The table where the errors are detected is not modified during the migration from IMatch 2021 to IMatch 2023.
Does the database function otherwise?

Can you upload the database to your cloud space and send me a link?
If not, contact me via email (support email address) and include a link to this topic.
I can send you a tool and some instructions so we can learn more about this specific analysis error.

I have opened a ticket in the database support forum. I have not seen this error before and I need more info.
Apparently, only your database is affected by this.

[hsegars]

The database seems to function fine. I am uploading the database file to dropbox and will send you a link once it is uploaded. Should I include the link in a reply or email the link to you?

[Mario]

You can email it directly to me (support email address). Please include a link to this topic so I know what's what.

I'm waiting for the database vendor to tell me how this error can happen and how to fix it.
I've never seen this before and I've checked my code and I don't write text to the oid column. May be as well a glitch in their diagnosis routine (since this was never reported before for your database).

[Mario]

I have analyzed the database and indeed, the table reported contains 279 oid values which the database considers as being text instead of a number. The other 14,139,642 values in the table are considered numeric.

The 'row id's of the 279 values are consecutive and fall somewhere in the middle  of the total number of rows.
All very strange.
I know how to fix the table in-situ and will send you instructions via email.