Access Performance Analyzer

[Jakboi]

Hello,

Have a few questions after I ran the Access performance analyzer. Now these ideas are they good or just some generic recommendations. Dont know if I should take care of all these or not?

Anyone know if I should do all these things and about how I should do it?

 

[The_Doc_Man]

In all cases when it says "IDEA - relate to other tables" it thinks (at least for the tables so noted) that a relationship might exist between the named table and some other table in the database, most often because two tables have fields with the same names, types, and sizes. Only you will know whether that is really true or true only by accident/coincidence.

Even if the possibility exists to form relationships between tables, only you can decide whether the relationships make any sense.

 

[Jakboi]

In all cases when it says "IDEA - relate to other tables" it thinks (at least for the tables so noted) that a relationship might exist between the named table and some other table in the database, most often because two tables have fields with the same names, types, and sizes. Only you will know whether that is really true or true only by accident/coincidence.

Even if the possibility exists to form relationships between tables, only you can decide whether the relationships make any sense.

Thanks that makes sense. Should I add the Option Explicit Statement or does that follow the same thought process?

 

[KeithG]

Option Explicit means that you must Dim each variable in the module you added it too. I believe this statement is suppust to speed up your code a little bit.

 

[The_Doc_Man]

True, Keith. I was looking at the other stuff.

The effect of the Option Explicit is two-fold.

First, you might find that you have some undeclared variables - due to being no better at spelling than I am. When you can't even spell your own variable names right, you are just screwed.

Second, undeclared variables are usually VARIANTS - which take much longer to use because of implicit format changes.

 

[Jakboi]

True, Keith. I was looking at the other stuff.

The effect of the Option Explicit is two-fold.

First, you might find that you have some undeclared variables - due to being no better at spelling than I am. When you can't even spell your own variable names right, you are just screwed.

Second, undeclared variables are usually VARIANTS - which take much longer to use because of implicit format changes.

Thanks again guys. Now from another post I read I add the Option Explict statement at the very top of the forms or where it says.

What exactly is it that I add?

Do I delete the compare database statement when I add the option explicit statement or do they both co exist?

 

[The_Doc_Man]

Co-exist. Put Option Explicit first, Compare Database second.

 

[Jakboi]

Co-exist. Put Option Explicit first, Compare Database second.

Thanks.

So then this would be correct and thats all?

Option Explicit
Option Compare Database

That is the top of my form in declarations.

 

[KeithG]

Does Option Explicit need to go first?

 

[The_Doc_Man]

Keith, it used to be required. Later versions may have relaxed that requirement. But then, my first version of Access was 2.0 on a Win3.1 system. So many versions later, who KNOWS what evil still lurks.

But there is always the reason that if you do it consistently, you will get into the habit and always remember to do both parts just because you become used to seeing them together. Any old memory aid in a storm, I always say as I gleefully mix my metaphors.

 

[pbaldy]

I have A2k & 2003. I have both set to add the Option Explicit automatically, and both put it below Option Compare Database. Thus I conclude that it doesn't matter anymore. Of course knowing the bad coding often practiced by M$, who knows?