[AccessD] Error 70

Jim Dettman jimdettman at verizon.net
Wed Aug 22 06:48:37 CDT 2012



 BTW, one of the things I did to my apps many years ago is apply line
numbering and use the undocumented VBA.Erl call in my error handling.
That's helped immensely in pinning down errors because it pin points an
error to a specific line of code.

  Line numbering can be added/removed using MZ Tools (and you can do a ton
more with it), which is free.

Jim. 

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Rocky Smolin
Sent: Tuesday, August 21, 2012 08:52 PM
To: 'Access Developers discussion and problem solving'
Subject: [AccessD] Error 70

Dear List:

I have an app - mde 2003 - runtime using Wise/Sagekey - so no Access
installed - - and had a user come up with an error that I've never had a
user report:

Error: 70 - Permission denied
In: frmMfrsXref.DisplayPartMaster

Never had this happen before and have had many users use this system for
years. Bit of a mystery.  The module frmMfrsXref.DisplayPartMaster reads
from a DAO recordset, but no writing.

Can anyone shed any light on what might have caused this?

MTIA

Rocky Smolin
Beach Access Software
858-259-4334
www.bchacc.com
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



More information about the AccessD mailing list