I want to increase speed!!!!HELP!!!!!

[akenaton]

Please give me an advice how to increase the speed of Access 2003 applications in network context when the application is used in the same time by more then 20 users.I tried to remove the beckend mdb on a different server but without any success!

Dan

 

[twoplustwo]

Stick it at the very top of the server pathname as opposed to it being buried.

Rename the backend to be.mdb and refresh table links.

 

[Guus2005]

Use replication and work local instead of working over the network. This usually is the bottleneck.
Use faster code. Drop all IIF's, DLookups in queries. Check for zero length strings rather than testing if a string equals "". etc...

 

[akenaton]

Please explain how to work localy...

I can't unerstand waht do you mean with "use a replicacation" and work localy...the date are the same for everybody, in backand...I have only the Frontend on each machine.Please help me!

Use replication and work local instead of working over the network. This usually is the bottleneck.
Use faster code. Drop all IIF's, DLookups in queries. Check for zero length strings rather than testing if a string equals "". etc...

 

[twoplustwo]

He means do you have a copy of the front end on each desktop per user

 

[akenaton]

I allready explain this...yes I have replications on each users machine...

He means do you have a copy of the front end on each desktop per user

 

[twoplustwo]

Then Try What I Suggested

 

[Guus2005]

Using the Access replication the database synchronizes with the master database. That's quite different than just a copy of your database!

 

[twoplustwo]

Guus,

I'm not sure if he actually means this...

 

[Guus2005]

My point was to work local, without the hassle of synchronizing everything by hand. Using the Access replication you can.

Working local usually increases speed. With local i mean on your C-drive.

 

[akenaton]

How to work localy when the users should update the same data? We are working localy with the Front End (forms, query, etc) but the main tables are shared on a drive named N (no important).I realy can't understand what do you mean in this case with "localy".

My point was to work local, without the hassle of synchronizing everything by hand. Using the Access replication you can.

Working local usually increases speed. With local i mean on your C-drive.

 

[twoplustwo]

"How to work localy when the users should update the same data"

You need to split the database - the Front End will look at the Back End tables. Put them on a server path rather than a lettered drive. This will avoid the risk of corruption. If everyone has a copy of the front end on their desktop or whatever they still access the same data. They just have their own version of the forms/queries/modules etc. on their machine (locally).

You could create an MDE after splitting so that queries/code etc. can't be viewed by the users.

All people using the SAME db is begging for corruption.

 

[boblarson]

A few things to consider:

http://www.fmsinc.com/free/NewTips/Access/LinkedDatabase.asp

http://www.granite.ab.ca/Access/performanceforms.htm

 

[Guus2005]

i was under the assumption that your database *was* split.

 

[akenaton]

I will try this...thank you all...you are very nice!

Thank you all...Now it's time to work...I will try all of the methods you give me......Thank you Bob for the articles!

 

[twoplustwo]

"you are very nice!"

 

[dfenton]

Replication is never a solution for performance problems. It introduces performance issues of its own (because of all the fields that have to be updated to track the replication information). Anyone who advises actually replicating the data on the workstations is someone who is not thinking clearly about the trade-offs between complexity and performance.