"Albert D. Kallal" <PleaseNOOOsPAMMkallal@msn.com> wrote in message news:<05Nqc.506825$Pk3.289512@pd7tw1no>...[color=blue]
> I would have loved to see the numbers for access 97 local also?
>
> That way, you could eliminate the network...and see if a2002 can perform ok?
> By not testing access97 locally, then you don't know if a97 is slower, or
> faster then a2002 on your local system? You see, if a2002 performs the same
> as a97 local.....then likely you can return a2002 performance back to a97
> levels. Perhaps a97 takes only 1 minute locally?
>
> There are few things about a2002 that will run slower (on the other hand, I
> been playing with computers for 20 years. Even when I had my first appleII,
> I can't EVER remember purchasing new software that did not take more disk
> space, more memory, simply required more resources? (can you think of ANY
> software you EVER purchased that ran better, and faster then the previous
> version..and used less of anything? I can't think of anything in the last 20
> years that has broke this experience of mine!). Perhaps you are new to
> computers, or never purchased or used new software?
>
> However, there are a few things to check. (in fact, quite a few..since a2002
> is 2 versions later then a97).
>
> First, queries with User defined functions can run a LOT slower. Try and
> avoid any VB function in a query. (this is a change in a2000 and later).
>
> The world is now a big place..and acess2000 and later uses uni-code to
> support international languages (text). That means for each character stored
> in the database...two characters are stored. All of office when to uni-code
> in office 2000, with the exception of Outlook..which finally made the change
> for a2003.
>
> This means that as a general rule...files are larger in a2000 and later
> (larger files = larger load on system).
>
> The other thing to check/change is things link track name auto correct (you
> REALLY want to turn this feature off!), and also try the trick of keeping
> the back end opened during this processing loop. So, when you load the front
> end...simply open a connection to some table in the back end..and KEEP this
> connection open. I would also test as a mde....
>
> Now run your stuff..it should run on par with a97.
>
> The list of performance got-ya's..and stuff like the "keep connection" open
> trick and how to get your performance back can be found here:
>
>
http://www.granite.ab.ca/access/performancefaq.htm[/color]
Albert,
Thanks for the tips.
On your link, you mention: 'sub datasheet Name property set to [Auto]
should be [None]' I'm new to Access 2002 and not familiar with how to
set this. Can you point me in the correct direction?
Thanks again.
