Jim, If the user does not have the proper access to the temporary folder you will get those errors.
Jan -----Original Message----- From: "Jim Belisle" <[email protected]> To: [email protected] (RBASE-L Mailing List) Date: Mon, 12 Jul 2010 07:12:48 -0500 Subject: [RBASE-L] - Re: access violation Jan, I do not use any “permissions” so this should not be a problem. Jim From: [email protected] [mailto:[email protected]] On Behalf Of jan johansen Sent: Monday, July 12, 2010 7:08 AM To: RBASE-L Mailing List Subject: [RBASE-L] - Re: access violation Jim, Do you use temp tables? If so does this one employee have the proper permissions to the temp location? Jan -----Original Message----- From: "Jim Belisle" <[email protected]> To: [email protected] (RBASE-L Mailing List) Date: Mon, 12 Jul 2010 06:09:18 -0500 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
