[AccessD] Error 70 - Permission Denied

Rocky Smolin rockysmolin at bchacc.com
Sun Mar 24 13:08:21 CDT 2013


Good idea.  I'll have them try that on Monday. TY

Rocky
 

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of John Bodin
Sent: Sunday, March 24, 2013 10:52 AM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Error 70 - Permission Denied

Have you eliminated user permissions in Windows?  If you get a user who is
not having the problem to log into the machine of the user with the problem
and run your app, does the error occur or not?  You can move forward from
there, knowing that it is something with the install on that workstation (if
new user has issues) or if not, then existing user may have windows
permission errors.  You could also have him/her try using program from
another working computer to see if that works or not.

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Rocky Smolin
Sent: Sunday, March 24, 2013 1:17 PM
To: 'Access Developers discussion and problem solving'
Subject: [AccessD] Error 70 - Permission Denied

Dear List:
 
I have a user using an app compiled in A2K3, using run-time from
Wise/Sagekey.  Back end is on the server, front end with run-time is
installed on each client.
 
All clients have been running fine.  One does not - many operations in the
app generate an error 70 - Permission denied.  The error is trapped by my
error trapping and a message box is displayed with options to email or fax
the error to me.  Then the app closes and must be restarted.  
 
An oversight - I left the control box on the message so the user has just
been minimizing the error box and carrying on (gotta fix that toot sweet).
The user finds that the transactions she was doing when the error is raised
are all complete and correct.  
 
They can't tell me exactly how long this has been going on or what might
have changed right before this problem started.  
 
I had them copy the back end to the client and relink the tables locally to
see if it was a problem on the server.  Still had the problem.  
 
Then I had them relink the tables to a local demo database to see if the
problem was in their back end.  Same problem.
 
All clients are running the same version of the app.
 
So I think I've eliminated the back end, the front end, and the server as
problems.  It would perhaps seem to be a question of the user account.  But
I really don't know where to look.
 
Any guidance on what might be causing the problem and where to begin
looking?
 
MTIA
 
Rocky Smolin
Beach Access Software
858-259-4334
www.bchacc.com <http://www.bchacc.com/> www.e-z-mrp.com
<http://www.e-z-mrp.com/>
Skype: rocky.smolin
 
 
 
--
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com

--
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com



More information about the AccessD mailing list