Allow me to clarify what I am looking for.

Setting or resetting the ANSI_PADDING value of the connection is simple enough, as you have pointed out.

For replication, it is necessary for the tables being replicated to conform to the same collection of SET options as for Indexed Views. As I'm sure you already know, these are:

ANSI_NULLS ON

ANSI_PADDING ON

ANSI_WARNINGS ON

ARITHABORT ON

CONCAT_NULL_YIELDS_NULL ON

QUOTED_IDENTIFIER ON

NUMERIC_ROUNDABORT OFF

These settings are associated with the table based on their values at the time the table was created.

Since our existing tables don't always conform to these settings, we have to take the steps, as part of the Snapshot, to manually modify the .sch files to correct and variances before applying the Snapshot to the subscriber.

Conceptually, what I'd like to know is, "Which existing tables don't have these settings correctly configured?"

sys.tables.uses_ansi_nulls does show me the settings for ANSI_NULLS. (So far, so good)

ObjectProperty() does show me the settings for ANSI_NULLS and QUOTED IDENTIFIER. (Hey, even better! But not all the way there.)

What I want is visibility into the other five settings (ANSI PADDING being my immediate concern) so that I, the user, can determine if I'm going to run into trouble when I replicate the table. SQL Server clearly has this information somewhere since it complains if the setting is wrong. Getting to this information is my quest.

The long term goal is to determine if it is worth while to re-configure any particular table to have the proper settings. Knowing the current configuration would be the first step in this process.