Form Buttons act Differently in Multiuser Envirnment

[mtairhead]

We recently put together a database for a call center. The file is located on a public drive, and all users seem to be able to access the file (at the same time) and input new information.

On one particular form, I've found an interesting problem: I've placed a button at the bottom of the form, which will go to a new record when clicked. The command to go to a new record is clearly in the OnClick event, however users in the call center have to click twice in order to execute the code. I don't have to.

We're using the same form, in the same file, opened with the same version of Access.

What's wrong with this database?

Thanks for any help you can give me,

Double-Clicking,

Andrew

 

[quest4]

Your users maybe the problem, no patients. Sometime network traffic can get heavy and conjested. This slows the packets down, somtimes tramically. User, especially ones who don't understand computers or networks and how they work, assume that something, like a control, is not working properly. When in fact it is just waiting to execute its' procedure. I hope I am making myself clear here.

 

[mtairhead]

I understand exactly. I'll be training this afternoon, and I'll observe the scene a bit more carefully, and report on the results

 

[quest4]

Maybe try it at night , when network traffic is light. If you have any problems then, run C&R and if the problem is still occuring, copy the code, and then delete the cmdButton. Creat a new cmdButton and replace the code. Run C&R again. Basically a little corruption of the old cmdButton may have occured, but not to likely. hth.

 

[The_Doc_Man]

Be aware of a couple of Windows "adjustments" that are in the control panel.

You can change the speed of a double-click.

You can change the INTERPRETATION of a double-click.

I would compare your settings vs. the users.

Path Start >> Settings >> Control Panel >> Mouse

There are also a couple of settings to consider regarding window behavior, though I don't recall that Access "cares" about traditional vs. active pages. But then, at the moment I'm in a slightly-behind-the-times environment.

Just a thought - and one that's easy to check.

 

[quest4]

Excellent point DocMan, I completely forgot about that. Thanks.

 

[mtairhead]

It seems that this mystery will never be solved: I went to test all of your suggestions only to discover that the problem no longer exists. I have made several changes to the database, including deleting an onInsert event (Perhaps the event caused this, since it was a new record the button was creating, and thus, inserting the old one into the dbase?) and I've unintentionally "corrected" the issue in the process.

Thank you all.

Andrew

 

[ghudson]

Something might have been throwing the focus to another object and the first click brought the focus back to the form in question.

Speed can also cause a problem as mentioned above. But that should not be an issue if the db is split and each user has a copy of the front end installed on their hard drive. The front end should never be shared on a network.