At 06:02 PM 1/3/2005 -0500, Karen Tellef wrote:
Am I the only one who's run into this? I don't remember seeing mention of this before. I just discovered that the SYS_ROWVER column in a table is considered a linking column for a form. Apparently versions 6.x just ignored this column, but not so with my version of 7.1? I'm not sure if the third party app we're using to connect to this database uses this column or not. If they don't, I can SET AUTOROWVER OFF and delete all the columns (they're in almost every table).
Karen,
It look like the database in question was once connected using Oterro to CREATE or ALTER tables.
FYI, SYS_ROWVER column is used, in most cases, by outside programs that do not have access to the internal R:BASE concurrency system (Table Locking, Row Locking, Qualcols, Column vs Row Verification and so on.)
When AUTOROWVER is set to ON, any CREATE TABLE or ALTER TABLE command adds the SYS_ROWVER column to the table being altered or created. The default in RBENGINE.CFG or RBASE.CFG is OFF. The default in OTERRO.CFG is ON.
The SYS_ROWVER column is a computed integer column that contains the version of the row. Its formula is as follows: (IFNULL((SYS_ROWVER+1),0,(SYS_ROWVER+1))).
This translates to the following: If the existing SYS_ROWVER is null then the row version is one. Otherwise increment the row version by one. Very useful feature to keep track of updates, etc at "Row Level".
Having explained that, in your case, you can DROP SYS_ROWVER column from all tables to avoid conflict of matching columns in form.
Hope that helps!
Very Best R:egards,
Razzak.
