Hello Members

I have split database. I used the Package wizard to set up an installation package for the FE which i installed on each of the user's PC about 7 users

The BE is on shared drive on the server .

The problem is that on some PCs, the db takes about 10 minutes to start. On my own PC, it takes less than 10 seconds . It is frustrating for me the developer and my users.

The start up code only checks linked tables . I also added a code to make persistent connection to the BE

All computers use Win XP SP3

Any pointers to the probable cause of the problem are highly appreciated.


Ronald

Hi Ronald

Are all users using the same version of Access that your db is deployed in and have only one version (the same one our db is in) of Access on their machines ?

If there's two version's of Access (eg A2003 and A2007) on the same machine, you can experience the symptoms you describe when opening a db in a different version

Hello Alan

All users /Pcs have Office 2007 installed .

The DB has a custom ribbon which does not work in earlier version of ms Access.

On first opening is very slow. If allow it to load, login and exit, the subsequent loading is Ok

The problem is random, may happen today, works ok for two more opening, and gets slow on tomorrow.

Ronald

Hi

If it's a random thing, does it happen at the same time when it happens ?

For example, if a machine that it occurs on loads fine at say 9.00am, but slows to a crawl if the db is opened at 10.00am, could there be something else that's running at the same time when it loads slowly, possibly a scheduled task, virus scan, backup, updater etc etc

Hello Alan

You a genius! (IMG:style_emoticons/default/uarulez2.gif)

We have Kasper sky anti virus. It auto scans the computer on start up.

I have started the scan and tried to start the Db, extremely slow. Stopped the scan. Started the DB, loaded fast.....

It is good now i know the cause.....

Thank you so much.

You have saved me because no one would have used a db that takes 10 minutes to load

Ronald

Hi

Great - glad you found the cause (IMG:style_emoticons/default/thumbup.gif)

I use Kaspersky AV and also it's installed on probably about 30/40 other PC's that I 'look after'. Depending on what version of Kaspersky you're running, there's an option in there that allows you to delay the auto 'quick' scan on start up by a user defined amount of time, which is great for a scenario like yours. If you delay the scan for say 2 or 3 minutes, it should give you time to open your db without the CPU having to fight for processing time with the AV

Hello

We use Kaspersky 6.0 for windows workstations

It it setup to automatic updates and to run a quick-scan at application start up. I have set the time to 5 minutes .


Let hope for the best


Ronald

Good luck (IMG:style_emoticons/default/thumbup.gif)