Horrible performance with additional users in 2007?

[vbaInet]

Are there any timers on any of the forms? Are there any scheduled tasks?
Do you have code that does some authentication for additional users, maybe checks whether a certain user is logged on? Try uncommenting such user authentication code

Try logging in as the Super Admin (or whichever term you use) and log in with another account that has read-only rights

 

[gemma-the-husky]

windancer - did you get this fixed?

i just had a similar problem with a database -

opening a persistent connection to a backend table has made all the difference to the performance.

 

[WinDancer]

FIXED!

The problem was reserved chars in the field names.

But having followed all the uggestions in the post, it now runs like the wind. It worked fine with a single user but no when more than one.

I have been using reserved chars in Access since 1996. I know to bracket those fields and it has NEVER been a problem. Access 2007 is a picky b!tch.

Thanks to all who tried to help- only 4 paydays left

Dave-

 

[pjs]

Shortly after Access was launched I attended an MS seminar/demo. When asked how many users could connect concurrently, the MS lady said "One". Turns out to be most honest words ever from an MS rep.
Don't believe the performance problem is all Access 2007's fault, could be some network glitches too.
To network 2 or more users, install Terminal Services and Remote Desktop. No performance issues, less data corruption and happy users.
The overhead of a conventional FE/BE LAN configuration is just too slow.

 

[pavlos]

Good structure of the db, meaning small tables through normalization and queries which do not use unnecessary fields, can significantly reduce the overhead between FE/BE

 

[gemma-the-husky]

Shortly after Access was launched I attended an MS seminar/demo. When asked how many users could connect concurrently, the MS lady said "One". Turns out to be most honest words ever from an MS rep.
Don't believe the performance problem is all Access 2007's fault, could be some network glitches too.
To network 2 or more users, install Terminal Services and Remote Desktop. No performance issues, less data corruption and happy users.
The overhead of a conventional FE/BE LAN configuration is just too slow.

I get acceptable performace from using a backend on a shared drive.

At another site that does use TS, we are actually now running into login problems, as the server hasnt got resources to statisfy all ther logons!

 

[Galaxiom]

The problem was reserved chars in the field names.

I have been using reserved chars in Access since 1996. I know to bracket those fields and it has NEVER been a problem.

Interesting that the reserved characters only caused trouble with the extra users. What were the characters and fieldnames you used?

Do you have any idea which part of processing actually slowed down.