John,
Thanks for the offer. I plan to be on site today or tomorrow so I can observe the user as she does this function. I have never used timers before but that may be something I need to implement in many areas. Some people (myself included) can be impatient and become click happy. Jim ________________________________ From: [email protected] [mailto:[email protected]] On Behalf Of John Engwer Sent: Monday, July 12, 2010 7:49 AM To: RBASE-L Mailing List Subject: [RBASE-L] - Re: access violation Jim, About a year ago I struggled with a similar problem. In my case, I isolated the problem to forms with DBGrids where I make use of the on click EEP. I discovered that some users would click multiple times (instead of once) causing various errors or erroneous results (including occasional access violations). To resolve the problem, I made use of the form timer to restrict the clicks to one. If your problem is similar to the problem I had, let me know and I will send you a copy of the code that I use. I am not in my office at the moment but I should be back around 2:00 PM and I will send it to you if you want to give it a try. John From: [email protected] [mailto:[email protected]] On Behalf Of Jim Belisle Sent: Monday, July 12, 2010 7:09 AM To: RBASE-L Mailing List Subject: [RBASE-L] - Re: access violation Larry, In the case you mentioned below, where the code worked fine with one PC but generated Access Violations on another PC, do you know if the problem was fixed? The one employee has no problems with the BOL form, while another employee constantly gets the Access Violations with the same form. Jim ________________________________ From: [email protected] [mailto:[email protected]] On Behalf Of Lawrence Lustig Sent: Thursday, July 08, 2010 12:21 PM To: RBASE-L Mailing List Subject: [RBASE-L] - Re: access violation << Any of you believe a server could be producing these errors? >> Bad data could cause that kind of problem. So if the server or the network is returning junk to the instance of R:Base running on the workstation, that could be responsible. And I have seen at least one instance where the exact same code running against the exact same database files worked on a PC and generated Access Violations (seemingly at random) on a networked copy of the database. -- Larry
