Changing database options - only some propagated to other databases?

[shira]

I hope I explain this question clearly.

I am trying to determine if making a change to a database option
(through Tools > Options) will only affect the database in which I am
making the change, or if the change will be propagated to all .mdb
files on my system.

Confusingly, from some initial testing, I found both instances of this
occurring. Here are examples of the results I saw.

Example A

Option: Track Name AutoCorrect (under the General tab)
Database1: feature is on
Database2: feature is on

I turn off feature in Database1. It remains on in Database2.

Example B

Option: Default field type (under Tables/Queries tab)
Database1: value is text
Database2: value is text

I change type to 'number' in Database1. When I open Database2, it the
type is now also 'number'.

Is there some method to the madness here? A consistent rule to know
when these settings are applied on the .mdb level or system-wide?

Thanks in advance!

 

[Jeff Boyce]

Some properties affect only the currently-open db; some affect all dbs; ...
and some give you the option of specifying whether you want one/all (see
4-year date setting)!

I'm sure (or at least hopeful) that someone, somewhere, has a rationale for
which properties are in which category... but I've never seen it <g>!

Good luck!

--
Regards

Jeff Boyce
Microsoft Office/Access MVP


Microsoft IT Academy Program Mentor
http://microsoftitacademy.com/

Microsoft Registered Partner
https://partner.microsoft.com/

 

[Rick Brandt]

I hope I explain this question clearly.

I am trying to determine if making a change to a database option
(through Tools > Options) will only affect the database in which I am
making the change, or if the change will be propagated to all .mdb
files on my system.

Confusingly, from some initial testing, I found both instances of this
occurring. Here are examples of the results I saw.

Example A

Option: Track Name AutoCorrect (under the General tab)
Database1: feature is on
Database2: feature is on

I turn off feature in Database1. It remains on in Database2.

Example B

Option: Default field type (under Tables/Queries tab)
Database1: value is text
Database2: value is text

I change type to 'number' in Database1. When I open Database2, it the
type is now also 'number'.

Is there some method to the madness here? A consistent rule to know
when these settings are applied on the .mdb level or system-wide?

Thanks in advance!

The vast majority of the option settings are for "your instance of Access on
your PC". You wouldn't expect making menu bar changes in Word for example to
follow your document onto someone else's PC right?

There are some options that are file specific. In most cases they are clearly
defined as such, but in a few cases (not so much).

The newer versions do a better job of making it clear which options affect the
file versus Access itself.