Is Table Partitioning certificated by QAD?

the table partitioning facility is transparent to the application except in one respect: you are allowed to change the value of the partition key during an update operation. when you do, this can cause the rowid of the row to change. some applications are not affected by that but not all. Only QAD can tell you if their application would be affected. They probably have not done enough testing to be able to answer definitively. To be safe, they may be cautious and say no. But it is up to them, not PSC.

@gus --

Is it also true that in a partitioned table the recid is no longer necessarily a unique identifier? Can two records in the same table, but in different partitions, have the same recid? But not rowid? So if your app is storing recid's (Why??) or using them to do unique FIND's, partitioning could break you app?

Find by recid for a partitioned table will silently failed. But Progress errors (e.g. 17390-17403) are still report the recids:

Index <index number> (<owner name>.<table name>, <index name><partition name>:<partition number>): Found invalid key <key value> recid <record identifier>.  (17403)

How to find a record knowing its recid and its partition number?

Thanks, Richard! I found an example how to use RowidGenerator in your "Table Partitioning - Application & Design" presentation, EMEAPUG 2014

emeapug.myweb2go.co.uk/sessions_2014.html