Object Dependencies

[Nymandus]

I have a database where track changes is turned off. When I click Object Dependencies Access wants me to turn track changes on. I have no problem with this provided it does not cause any issues. My understanding was that track changes can increase your database design as well as slow it down.

My concerns are:

1) This database is already active with multiple people between two locations (central U.S. and East Coast) using the front-end. Does turning on track changes cause problems when added to a database?

2) Does the fact that I have the database split to front-end and back-end make a difference?

3) Do I need to do this from the back-end or can it be done from my front-end?

4) Do I need to be in exclusive mode?

5) Is this easily reversable? I really only want to know the interplay of the Tables, Reports, Queries and Forms so that I can make changes and know everything else that will need to be changed.

6) I read that track changes will automatically make changes to your reports, queries and forms but not formulas and macros... is this true?

 

[CJ_London]

As with all these things, take a copy before you start and if you are not sure what you are doing, work on a copy until you understand all the implications

My understanding was that track changes can increase your database design as well as slow it down.

Correct

1) This database is already active with multiple people between two locations (central U.S. and East Coast) using the front-end. Does turning on track changes cause problems when added to a database?

Providing they are each using their own copy of the front end then no, it only affects the db you are working on. If they are all using the same copy of the front end, you are likely to get corruption problems at some point down the line regardless of tracking.

2) Does the fact that I have the database split to front-end and back-end make a difference?

The back end only consists of tables so there is no tracking unless you are using lookups in your tables which is a bad idea. Tracking is in the front end and would relate to your linked table object, not the actual table so if you are making changes to table field names it will have no benefit.

3) Do I need to do this from the back-end or can it be done from my front-end?

not sure what you mean byt this but as from above - the front end

4) Do I need to be in exclusive mode?

you don't need to be in exclusive mode so far as I am aware

5) Is this easily reversable? I really only want to know the interplay of the Tables, Reports, Queries and Forms so that I can make changes and know everything else that will need to be changed.

No. So far as I am aware once you turn tracking on 'the damage is done'. This certainly was the case for 2003 and earlier, not sure about 2007 and later - I have the habit of turning tracking off as I found it has limited benefits except perhaps for small 'lay' projects

6) I read that track changes will automatically make changes to your reports, queries and forms but not formulas and macros... is this true?

It's true as far as it goes, but it won't make changes to vba code or subqueries used in queries which in turn may be used in forms and reports. Similarly changing the name of a field in a table in the back end will not update your front end - see 2 above.

 

[Nymandus]

thank you,

I made the copy and set up the dependencies...I was able to see what I needed. the copy was 1 meg larger than the original... for now I am keeping this copy in the backround for reference.

If I continued to use it would that continue to get larger or does that just depend on the compexity of added forms, queries and reports?

 

[CJ_London]

you can try compacting to reduce the size

If I continued to use it would that continue to get larger or does that just depend on the compexity of added forms, queries and reports?

I expect so - as I said, I haven't used it for years so cannot speak from experience