Show a "loading" message while database is opening

[janeyg]

Hi
I have a split database with multiple users. Since I split the database, it runs slower than the unsplit version. I understand this happens. I would like to have a message pop up when the database is loading. It takes approx 2 mins to load. Users get impatient and start clicking. So, I wanted to have a message pop up to let them know it is opening.

Is there a way to do this? I have the same problem with forms loading, I have 5 forms and each takes about 4 secs to load, so thought about a loading message there too.
thanks
Janeyg

 

[Trevor G]

Create a form with a message on it add a timer event like 3000 mil seconds and then in the timer event you can then close the form after the 3 seconds and then open the first part of the database then set the open to open the new form first.

 

[RainLover]

We should be looking at why it is taking so long. This is not normal.

Do you know of any reason why this is happening.

If interested in following through with this please explain your structure. Namely where is the back end and where is the front end.

 

[janeyg]

Hi Rain

I dont know why it takes so long. I have read other posts of this happening to other people but I can't seem to find an answer.

The split database takes approx 2 - 2 1/2 minutes to load. The front and back end sits on a shared server. Each user has their own copy of the front end. I tried placing their front end copy directly on their pc or in their own folder on the shared server. But it still takes 2 minutes or so to load

When more than one person opens the database it take the above time to load. If you are the first one in the database - it takes about 15 secs. My users are frustrated by having to wait a couple of minutes for it to load, yet I dont know what to do.


Am I doing something wrong?
thanks
Janeyg

 

[janeyg]

oh, also I made the front end an accde file before copy it for each user. The front and back end are only 250mb each. It is not a big database.

Is there anything else I can tell you to help?
thanks

 

[RainLover]

I don't know what is wrong. It is a matter of tracking down the problem.

Typically the front end resides on the user's machine in their C:\ Drive.

The back end resides on the server in a shared folder.

First thing to do is to time how long it takes to load the Back End. Then how long does it take to open your largest Table. These should be immediately but please do a test and let me know the outcome.

While you are at it make sure the back end is not burried deep into a folder.

Z:\MyDatabase\TestDatabase.mdb is better than Z:\My\Data\Base\Location\2003\Arts\Dept\TestDatabase.mdb

 

[pr2-eugin]

250 mb front end? Do you have temporary tables stoed on the frontend? Have you performed 'Compact and Repair'? on both front end and backend?

 

[janeyg]

ok, the folders may be burried deep. Very difficult as we have a large shared server with team folders, certain folder with access restrictions. So it looks like this

S:\Services\Our Team Name\BOB Database\Split Database\Front End
S:\Services\Our Team Name\BOB Database\Split Database\Back End

Back end takes 5 secs to load
Biggest table takes 2 secs to load

So back end loads pretty much immediately

 

[RainLover]

That is not really acceptable. 5 Secs to load almost nothing is a long time.

What if both Front and Back ends were on the Client's C:\Drive. This should be very quick.

Are you running any code on start up.

 

[janeyg]

I regularly 'Compact and Repair' the back end, once per month and do a back up.

I made an accde file of the front end to distribute which is 8.96mb.

I saw advice on not performing a 'Compact and Repair' on the front end whe I originally split it. So before I split the database, I did a compact and repair, split the database. Do a compact/repair and back frequently, then made the accde file which I copied and distributed to users.

Was that bad advice? Should I compact and repair the front end at the same time as doing the back end?

 

[janeyg]

I am part of the team that uses the database. I was told the back should sit on a shared server. Sorry, I dont know what you mean about moving or copy the back
end?

I am one of the muliple users accessing the database. There are about 8 of us using the database.

Just going to check for opening code.

 

[RainLover]

The Front End only changes when you add new features. A back up of the original is all you need.

The Back end changes with every data entry. This needs to be backed up regularly. At least Daily. Compact and repair is not really required very often. Always back up before doing so. once a month should be enough unless you are having problems. In which case you need to address what ever problem you have. Compact and Repair does exactly that. It repairs. A good Database should never require repairing.

My suggestion in the last post was to put both Front and Back ends on the one machine to test for speed. Don't forget to relink the tables to the new location.

I am going off line soon. Will come back later to check on your progress.

Please check to see if anything is happening on start up.

 

[janeyg]

I do have a code which logs users on and off the database and shows who is logged in. I found it on here called User Logging.mdb

I just imported the table, forms and module into my database.

 

[janeyg]

It will do a test

 

[PiedPiper70]

It sounds like an issue with something which is running at start up. so can I suggest you try temporarily disabling the logging function that you are running and seeing if that makes a difference.

Dave

 

[janeyg]

Thanks dave, I will give that a try too

 

[mahenkj2]

did you run Performance analyzer in Database tools. Just some point from me in between.

 

[RainLover]

Why would you want to know who is logged in.

If you want to know from time to time just open the Lock File. It will open in note pad.

You could log who made changes. This is easy to do and would not use valuable resources.

So disable that current login as suggested. What difference does that make.???

 

[janeyg]

I will do a test on disabling it to see if it makes any difference. It is enabled because the database if used by people in different parts of the building and we experience problems with people locking a field and leaving there desk for long period or forgetting they are in the record, thus stopping other users from updating info. By seeing who is logged in, we can just messenger the user and ask them to come out of the field. I have set up record locking as we have multiple people adding data.

I will try also running another analyze performace. This only flagged ideas last time but I will run another.

thanks for all the suggestions, I will try and see what happens!

 

[janeyg]

Yes, you were right. I totally forgot that I had a report loading at the start. I have switched this off and ran the performance analyzer, applied the suggestions and this is now running much quicker.

thanks to all for your help and suggestions