-- Representative pattern: clsAttorneyConflict RetrieveSQL (one of 8 TableMaint reference-- objects in this consolidated group), reconstructed verbatim from-- SAIF.Business.Claim.Legal\TableMaint\clsAttorneyConflict.vb:SelectATTORNEY_CONFLICT.ATTORNEY_CONFLICT_SEQ_NUMasAttorneyConflictSeqNum,ATTORNEY_CONFLICT.ATTORNEY_EMPLIDasAttorneyEmplid,ATTORNEY_CONFLICT.EFF_DATEasEffDate,ATTORNEY_CONFLICT.EXP_DATEasExpDate,to_char(ATTORNEY_CONFLICT.CONFLICT_LEGAL_PERSON_SEQ_NUM)asConflictLegalPersonSeqNum,to_char(ATTORNEY_CONFLICT.ATTY_PROVIDER_LOCATION_SEQ_NUM)asProviderLocationID,ATTORNEY_CONFLICT.ADJUSTER_EMPLIDasAdjusterEmplid,ATTORNEY_CONFLICT.POLICY_NUMasPolicyNumFromATTORNEY_CONFLICTWhereATTORNEY_CONFLICT.ATTORNEY_CONFLICT_SEQ_NUM=:AttorneyConflictSeqNum-- plus matching Insert/Update/Delete statements and a Create-sequence Select per object.-- Each of the other 7 TableMaint objects listed above repeats this same CRUD shape against-- its own table (see database-tables.md for the per-table column detail); the exact column-- lists for those other 7 objects were **not individually reconstructed here — consolidated-- to avoid ~40 near-duplicate single-purpose pages, per the DB analysis's own consolidation-- approach. Treat the non-clsAttorneyConflict statements as unverified until inspected-- directly against their respective .vb source files.