Updating Access Database fields ?

Hello again,
I am coming to the end of my first substantial VB6 project with ADO and MSAccess 2002 and upon looking over the update code (in others updating the databases) I see that for various reasons the procedures I have written will update say field 1, then field 100, then field 3, and so on (out of chronological order) based on form layouts etc., it would be a task to order these in database order (field 1, then field 2, then field 3, and so on) I have some substantial tables (150 or more fields) my question is it worth redoing the code (for say system performance, speed, durability,etc) to bring them into numeric order?
Any opinion will help.
thanx
mbhey101Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Patrick MatthewsCommented:
Hi mbhey101,

The order in which the updates occur is probably not all that significant.

The thing that stands out to me is:

> [...] I have some substantial tables (150 or more fields) [...]

Why so many fields?  Having that many fields in a single table is usually an indicator of a denormalized database
design; if this is true, then that points to potential headaches down the road...

Regards,

Patrick

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
mbhey101Author Commented:
"Why so many fields?  Having that many fields in a single table is usually an indicator of a denormalized database
design; if this is true, then that points to potential headaches down the road..."

Well I am suspecting a few headaches but I hope not to many, I will find out soon though.

What is or (are the characteristics of a "denormalized database")?


Patrick MatthewsCommented:
> What is or (are the characteristics of a "denormalized database")?

At the risk of sounding like Justice Potter Stewart, I have trouble articulating it, but I know it when I see it :)

For a quickie on normalization, see:
http://databases.about.com/od/specificproducts/a/normalization.htm

One thing to look for is whether you use multiple fields on a single column to express a certain attribute.
Without being able to see your schema, it would be tough for me to know whether your design is normalized
(good) or denormalized (bad).  However, in typical normalized databases, it is rare for tables to have more
than about two dozen fields (and usually many fewer than that!).

Patrick
mbhey101Author Commented:
OK, I will read and take note of the article-and Probaly learn something.
Thanx
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Visual Basic Classic

From novice to tech pro — start learning today.