I had a similar problem--my app ran quite well in A97, but was way slow in

A2K.  I ended up having to attack it from a couple of different angles.  Two

things that made a noticeable difference for me were turning off Name

AutoCorrect (nice feature but boy howdy, what a pig) and changing all the

subdatasheet properties for tables to [None].



If you do a KB search specifying Access 2000 as the product, using just the

word 'slow' as a search term you'll get about 25 articles, almost all of

which are worth reading (both of the above fixes are in the list).  The KB

is at



http://search.support.microsoft.com/kb



See also the help file's 'optimize performance' topics (there's one for

forms, one for tables, etc.)--those things are worth doing too.



HTH,



-Roy



-----Original Message-----

From: Susan Henesy [mailto:susan.henesy@w...]

Sent: Tuesday, August 28, 2001 12:20 PM

To: Access

Subject: [access] RE: Do Front-End/Back-End Databases REALLY speed

things - up?





Hi everyone,



I've got a new problem now!



I was given a chance to visit someone's Office 2000 PC, and gave a couple 

of the A2K front-ends a try. 



On the first database:  EXTREMELY SLOW.  Completely totally unacceptably 

and unbelievably slow!  The employee has a Pentium II, whilst I have a 

Pentium III, but I don't know if that should make it as awful as it was.  

I also copied the front-end to the user's C: drive and that didn't improve 

it one bit.  Oh my.  If this is to be the performance -- my company isn't 

going to let me get away with it.



Has anyone experienced this problem?  



On the other A2K database front-end, the database wouldn't open up a 

report.  I got a "debug" message that said it couldn't perform the 

action.  The "action" was nothing more than: 



DoCmd.ShowToolbar "Form View", acToolbarNo



This is totally acceptable according to A2K Help Files, so why is the code 

breaking here?  A2K *does* have a "Form View" toolbar, so whassup with 

*that*?



Even when I programmed it to "Resume Next" upon hitting that error, it 

tied up the system until we finally had to ALT-CTRL-DELETE it.



Help?!



Susan

Thank you, Roy!



But...auuugh.  I opened up my back-end db and copied the code for setting 

the subdatasheet properties to NONE, and it worked, too, despite the fact 

that my back-end is in Access '97 and when I clicked on VIEW PROPERTIES 

via the manual method, there was no discernible "subdatasheet name" 

option.  Um, alrighty then, hope those tables are ok!



The things that are really slow on one of these forms are the combo 

boxes.  So, I used real queries instead of SELECT statements (per another 

optimization suggestion), but the boxes are still populating very slowly.



And Name/AutoCorrect is unchecked, so that's not it.



Perhaps it's a combo of Pentium II and the server?  I've copied the 

Northwind.mdb database to the server and split it -- we'll see if it fares 

any better.



'Til then, any other suggestions you can think of will be greatly 

appreciated, trust me!



Susan

Well, well, well.



I think that the server where I keep my ASP databases actually performs a 

little better.  I put a copy of the back-end on THAT server and I am 

already seeing improvements.  You know... ever since the tech guys moved 

our databases to the NT network drive, the databases have been acting 

worse, not better.  We were told it was probably due to an increase in 

traffic.  *I* think that, despite the arguments that the NT servers are 

bigger and more reliable... they just might suck!  



I've got to do my best to get the speed to improve a LITTLE bit, at 

least.  Thanks for pointing me in the direction of those files, Roy!



Susan

I only caught this last message in the stream but here's my 2c.



We develop apps using Access 97 & 2000.  Last week we had to convert one

to Access XP, as that was what the client was running.  Initial

observations were that Access XP ran faster than 2000.  If this is an

option for you, you may want to get your paws on a copy and give it a

burl.



Padgett



-----Original Message-----

From: Susan Henesy [mailto:susan.henesy@w...] 

Sent: Wednesday, 29 August 2001 1:21 AM

To: Access

Subject: [access] Re: slow performance w/A2K



Well, well, well.



I think that the server where I keep my ASP databases actually performs a 

little better.  I put a copy of the back-end on THAT server and I am 

already seeing improvements.  You know... ever since the tech guys moved

our databases to the NT network drive, the databases have been acting 

worse, not better.  We were told it was probably due to an increase in 

traffic.  *I* think that, despite the arguments that the NT servers are 

bigger and more reliable... they just might suck!  



I've got to do my best to get the speed to improve a LITTLE bit, at 

least.  Thanks for pointing me in the direction of those files, Roy!



Susan

You can also gain a small amount of performance gain if you optimise the

server for "File Sharing".



It's not a huge gain, but it all adds up.







-----Original Message-----

From: Susan Henesy [mailto:susan.henesy@w...]

Sent: Wednesday 29 August 2001 01:21

To: Access

Subject: [access] Re: slow performance w/A2K





Well, well, well.



I think that the server where I keep my ASP databases actually performs a

little better.  I put a copy of the back-end on THAT server and I am

already seeing improvements.  You know... ever since the tech guys moved

our databases to the NT network drive, the databases have been acting

worse, not better.  We were told it was probably due to an increase in

traffic.  *I* think that, despite the arguments that the NT servers are

bigger and more reliable... they just might suck!



I've got to do my best to get the speed to improve a LITTLE bit, at

least.  Thanks for pointing me in the direction of those files, Roy!



Susan

Happy to be of service.



Speaking of NT--see the KB article on using a server that's at a different

service pack level than the client.  That wasn't an issue for my app, but if

your users are running NT, then it's worth looking at.



HTH,



-Roy



-----Original Message-----

From: Susan Henesy [mailto:susan.henesy@w...]

Sent: Tuesday, August 28, 2001 6:21 PM

To: Access

Subject: [access] Re: slow performance w/A2K





Well, well, well.



I think that the server where I keep my ASP databases actually performs a 

little better.  I put a copy of the back-end on THAT server and I am 

already seeing improvements.  You know... ever since the tech guys moved 

our databases to the NT network drive, the databases have been acting 

worse, not better.  We were told it was probably due to an increase in 

traffic.  *I* think that, despite the arguments that the NT servers are 

bigger and more reliable... they just might suck!  



I've got to do my best to get the speed to improve a LITTLE bit, at 

least.  Thanks for pointing me in the direction of those files, Roy!



Susan