By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
455,479 Members | 1,607 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 455,479 IT Pros & Developers. It's quick & easy.

Upgrading to 2003

P: n/a
I am a relatively new user. My position is to maintain an Access DB
that is running in a multi user enviornment and split on a network
running Front(2K and 97) and BE(97). The DB has been used for a number
of years and has grown tremendously. I have been asked to normalize a
Supplier table that has really gotten out of hand with duplicate
records(no primary key). With all of the Forms and Reports coming from
this database, I was trying to figure out how things may affect one
another. I was reading that the 2003 version of Access has an "Object
Dependency" function that will define this information. If I run the
2003 version on my computer, should I only use it to determine the
Object Dependencies and continue to run the 2K version for updates and
changes, Or can I just use the 03 version and back the database down
for the other users.
Does this make sense?
Thanks in advance for your help.
Jeff

Nov 13 '05 #1
Share this Question
Share on Google+
2 Replies


P: n/a
Jeff, if you are feeling brave and have time to waste, you can make a *copy*
of the database and try the Object Dependency stuff.

I tried this once on a database that had known problems such as queries that
referred to tables that had been deleted. I wrote some code to identify
these invalid dependencies, but was unable to get the code to run to
completion. Access 2003 constantly crashed (shut down by Windows), and it
proved to be an utterly fruitless exercise in frustration.

Probably a major part of the problem is that this Object Dependency stuff
relies on Name AutoCorrect, which is still so full of holes as to be a major
disaster zone in Access. If you are not aware of these issues, we have
listed a few of the earlier problems at:
http://allenbrowne.com/bug-03.html
and I'm not bothering to keep that up to date with new problems... just
enough to let you know to stay away from this mis-feature.

There are other 3rd party utilities that do work, e.g. you will often see
Speed Ferret recommended in these groups.

--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

<la******@nationwide.com> wrote in message
news:11*********************@g47g2000cwa.googlegro ups.com...
I am a relatively new user. My position is to maintain an Access DB
that is running in a multi user enviornment and split on a network
running Front(2K and 97) and BE(97). The DB has been used for a number
of years and has grown tremendously. I have been asked to normalize a
Supplier table that has really gotten out of hand with duplicate
records(no primary key). With all of the Forms and Reports coming from
this database, I was trying to figure out how things may affect one
another. I was reading that the 2003 version of Access has an "Object
Dependency" function that will define this information. If I run the
2003 version on my computer, should I only use it to determine the
Object Dependencies and continue to run the 2K version for updates and
changes, Or can I just use the 03 version and back the database down
for the other users.
Does this make sense?
Thanks in advance for your help.
Jeff

Nov 13 '05 #2

P: n/a
Thanks for the input Allen. Very helpful. I will pursue one of the
third party software products.
Allen Browne wrote:
Jeff, if you are feeling brave and have time to waste, you can make a *copy*
of the database and try the Object Dependency stuff.

I tried this once on a database that had known problems such as queries that
referred to tables that had been deleted. I wrote some code to identify
these invalid dependencies, but was unable to get the code to run to
completion. Access 2003 constantly crashed (shut down by Windows), and it
proved to be an utterly fruitless exercise in frustration.

Probably a major part of the problem is that this Object Dependency stuff
relies on Name AutoCorrect, which is still so full of holes as to be a major
disaster zone in Access. If you are not aware of these issues, we have
listed a few of the earlier problems at:
http://allenbrowne.com/bug-03.html
and I'm not bothering to keep that up to date with new problems... just
enough to let you know to stay away from this mis-feature.

There are other 3rd party utilities that do work, e.g. you will often see
Speed Ferret recommended in these groups.

--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

<la******@nationwide.com> wrote in message
news:11*********************@g47g2000cwa.googlegro ups.com...
I am a relatively new user. My position is to maintain an Access DB
that is running in a multi user enviornment and split on a network
running Front(2K and 97) and BE(97). The DB has been used for a number
of years and has grown tremendously. I have been asked to normalize a
Supplier table that has really gotten out of hand with duplicate
records(no primary key). With all of the Forms and Reports coming from
this database, I was trying to figure out how things may affect one
another. I was reading that the 2003 version of Access has an "Object
Dependency" function that will define this information. If I run the
2003 version on my computer, should I only use it to determine the
Object Dependencies and continue to run the 2K version for updates and
changes, Or can I just use the 03 version and back the database down
for the other users.
Does this make sense?
Thanks in advance for your help.
Jeff


Nov 13 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.