OI/Arev32 and SQL compliance

KDIV

I have a theoretically question, I was wondering if anyone had any input or experience. Does an Arev application (version prior to v3.12) have to be SQL compliant with naming convention before porting to AREV32 and OI? Back in the day (OI v2.x) our Arev v3.12 application has to be SQL compliance with naming conventions before we could port over to OI. That meant the 'dots' had to be out of table names, dictionary items and program names. Does that same rule apply to porting an Arev application to AREV32? If yes, how can the Arev routines with dots in the name, dots in the table names and dots in the dictionary items in AREV32 run? If no, is there any issues to be aware of? TIA.

DonBakke

The answer is yes and no. OI itself requires SQL compliant naming conventions as it always has. However, in order to ease the porting of AREV to ARev32, Revelation created the CTODICT.MFS. This will get installed on your dictionaries when you do the Arev32 Conversion. Doing this allows your processes to still work with the dot naming convention but internally the MFS converts these to underscores so OI can do its job.