I believe this issue is a result of a recent update to MS Office/Access or Windows 10. When I run this code:
Dim s As String
With CreateObject("Scriptlet.TypeLib")
s = Left(.Guid, 9)
newguidx = Right(s, 8)
End With
I get an error: Permission Denied on the With Statement. This is new only only cropped up after my admins updated our systems. I have no option to roll back updates. Anyone come across this and have a work around?
OS: Windows 7 Enterprise
Access Version: 2010
Thanks
asked Jul 26, 2017 at 16:13
From Microsoft:
This issue is by design, as of the July security updates. This control is blocked as a security measure to help prevent malicious code from running in Office applications. We are working on getting a knowledgebase article out with the recommended method. Until that KB is ready, I’ll post the content here:
Workaround
The preferred method is to change the code to use Windows API CoCreateGuid (https://msdn.microsoft.com/en-us/library/windows/desktop/ms688568(v=vs.85).aspx) instead ofCreateObject("Scriptlet.TypeLib").Guid
' No VT_GUID available so must declare type GUID
Private Type GUID_TYPE
Data1 As Long
Data2 As Integer
Data3 As Integer
Data4(7) As Byte
End Type
Private Declare PtrSafe Function CoCreateGuid Lib "ole32.dll" (Guid As GUID_TYPE) As LongPtr
Private Declare PtrSafe Function StringFromGUID2 Lib "ole32.dll" (Guid As GUID_TYPE, ByVal lpStrGuid As LongPtr, ByVal cbMax As Long) As LongPtr
Function CreateGuidString()
Dim guid As GUID_TYPE
Dim strGuid As String
Dim retValue As LongPtr
Const guidLength As Long = 39 'registry GUID format with null terminator {xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx}
retValue = CoCreateGuid(guid)
If retValue = 0 Then
strGuid = String$(guidLength, vbNullChar)
retValue = StringFromGUID2(guid, StrPtr(strGuid), guidLength)
If retValue = guidLength Then
' valid GUID as a string
CreateGuidString = strGuid
End If
End if
End Function
Alternate Workaround
This will allow you to use
CreateObject("Scriptlet.TypeLib")however it will lessen the security protection added by the Office July 2017 security update.
You can set a registry key that will allowScriptlet.TypeLibto instantiate inside of Office applications. When this registry key is set, Office will not block any use of this COM control.
- Open Registry Editor.
- Go to: Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\16.0\Common\COM Compatibility{06290BD5-48AA-11D2-8432-006008C3FBFC}
- Note: you may need to search the registry to find the correct location under HKEY_LOCAL_MACHINE based on your installed Office version.
- Add ActivationFilterOverride
- Set DWORD: 1
Detailed Instructions:
- Click Start, click Run, type regedit in the Open box, and then click OK.
Locate and then click the following key in the registry:
HKEY_LOCAL_MACHINE- On the Edit menu, point to Find, and then enter the following in the Find What: text box:
COM Compatibility- Ensure Keys is selected, and Values and Data are deselected. Next select Match whole string only, click Find Next
Locate and then click the following key:
{06290BD5-48AA-11D2-8432-006008C3FBFC} Note: if the key is not present you will need to add it. On the Edit menu, point to New, and then click Key. Type in {06290BD5-48AA-11D2-8432-006008C3FBFC}- On the Edit menu, point to New, and then click DWORD (32-bit) Value
- Type ActivationFilterOverride for the name of the DWORD, and then press Enter.
- Right-click ActivationFilterOverride, and then click Modify.
- In the Value data box, type 1 to enable the registry entry, and then click OK.
- Note to disable the ActivationFilterOverride setting, type 0 (zero), and then click OK.
- Exit Registry Editor, and then restart any open Office application.
chris neilsen
52.5k10 gold badges85 silver badges123 bronze badges
answered Jul 26, 2017 at 16:35
David ZemensDavid Zemens
53k11 gold badges81 silver badges130 bronze badges
7
In Access, we can suffice with this very short function to generate a GUID by leveraging Application.StringFromGUID to cast bytes to a GUID. It generates pretty verbose GUIDs, though, with the format {guid {00000000-0000-0000-0000-000000000000}}.
Declare PtrSafe Sub CoCreateGuid Lib "ole32" (ByVal GUID As LongPtr)
Public Function NewGUID() As String
Dim b(15) As Byte
CoCreateGUID VarPtr(b(0))
NewGUID = Application.StringFromGUID(b)
End Function
You can strip away unwanted characters, for example by replacing the last line of this function with NewGUID = Mid(Application.StringFromGUID(b), 8, 36). Then, the format will be 00000000-0000-0000-0000-000000000000
answered Oct 17, 2018 at 12:02
Erik AErik A
31.7k12 gold badges42 silver badges67 bronze badges
Since windows update taken out «Scriptlet.TypeLib», try the following:-
Declare Function CoCreateGuid Lib "ole32" (ByRef GUID As Byte) As Long
Public Function GenerateGUID() As String
Dim ID(0 To 15) As Byte
Dim N As Long
Dim GUID As String
Dim Res As Long
Res = CoCreateGuid(ID(0))
For N = 0 To 15
GUID = GUID & IIf(ID(N) < 16, "0", "") & Hex$(ID(N))
If Len(GUID) = 8 Or Len(GUID) = 13 Or Len(GUID) = 18 Or Len(GUID) = 23 Then
GUID = GUID & "-"
End If
Next N
GenerateGUID = GUID
End Function
Alternatively,
if you are connecting to SQL Server 2008 or higher, try to use the SQL NEWID() function instead.
answered Jan 25, 2018 at 2:56
rchackorchacko
1,95523 silver badges24 bronze badges
- Remove From My Forums
-
Вопрос
-
I have an Access 2010 shared database. It has been using for long time and fine. Users have admin right on their pcs. Start few months ago, some users began upgrade to Window 10 with Access 16 and been installed Access 2010
as plus. We direct every user uses Access 2010 for this dB. Everything looked fine till last week. Some Window 7 / Access 2010 users started seeing Error: 70 Permission Denied message. There has been no change on that Access database. Can you light me
up the possible root cause? Thanks a lot!
- Remove From My Forums
-
Question
-
Hi Friends
I am using MS Access DataBase for my Application.
On the User InterFace as soon as i click on the ComboBox i start getting the the Error Message :
Runtime Error ’70’ Permission Denied.On the RowSource Property of ComboBox my setting in an Select Query.
I need Help on this, i have also checked the DCOM Properties.
Thanks And Regards
Sagarr
Answers
-
Well, I came accross this thread:
http://www.microtools.us/SupportFAQs.htm#QB16
-17. How can I fix the Run-time error ’70’: Permission Denied?
A: Your computer may not have the necessary registry information for the class «Access.Application». Please run regedit to search Access.Application class. If it’s missing you may need to repair your Access. If you are running our converters on a Vista system
you need to run them as Administrator.Hope this helps,
Daniel van den Berg | Washington, USA | «Anticipate the difficult by managing the easy»
-
Marked as answer by
Thursday, October 13, 2011 8:02 AM
-
Marked as answer by
Are you trying to use Microsoft Access, but are you getting the error ’70 permission denied’?
Tech Support 24/7
Ask a Tech Specialist Online
Connect with the Expert via email, text or phone. Include photos, documents, and more. Get step-by-step instructions from verified Tech Support Specialists.
On this page, you will find more information about the most common causes and most relevant solutions for the Microsoft Access error ’70 permission denied’. Do you need help straight away? Visit our support page.
Let’s get started
It has never been easier to solve error «70 permission denied».
View list of solutions
Contact an expert
Error information
How to solve Microsoft Access error 70 permission denied
We’ve created a list of solutions which you can follow if you want to solve this Microsoft Access problem yourself. Do you need more help? Visit our support page if you need professional support with Microsoft Access right away.
Tech Support 24/7
Ask a Tech Specialist Online
Connect with the Expert via email, text or phone. Include photos, documents, and more. Get step-by-step instructions from verified Tech Support Specialists.
Need more help?
Do you need more help?
Tech experts are ready to answer your questions.
Ask a question
 |
Error Number: | Error 70 |
| Error Name: | Access Error 70 Permission Denied | |
| Error Description: | Error 70: Microsoft Access has encountered a problem and needs to close. We are sorry for the inconvenience. | |
| Developer: | Microsoft Corporation | |
| Software: | Microsoft Access | |
| Applies to: | Windows XP, Vista, 7, 8, 10, 11 |
Description of Access Error 70 Permission Denied
Experts generally refer to Access Error 70 Permission Denied as a «runtime error». The Microsoft Corporation developers typically evaluate Microsoft Access with a series of modules to remove bugs to meet industry standards. Although these preventive actions are taken, at times errors like error 70 will be missed.
Microsoft Access users can face an error message after execution the program such as «Access Error 70 Permission Denied». If Access Error 70 Permission Denied occurs, developers will be told about that issue though error reporting built-into the application. Microsoft Corporation will then correct the errors and prepare an update file for download. Therefore, when you encounter a prompt for a Microsoft Access update, it is usually because it’s a solution for fixing error 70 and other bugs.
Why Runtime Error 70 Occurs?
The most common occurrences Access Error 70 Permission Denied problems is when loading up Microsoft Access. These are the three major triggers for runtime errors like error 70:
Error 70 Crash — Error 70 can lead to total program freeze, which prevents you from doing anything. This usually happens when Microsoft Access can’t handle the provided input, or when it doesn’t know what to output.
Access Error 70 Permission Denied Memory Leak — This type of memory leak causes Microsoft Access to keep using increasing amounts of memory, bringing down the total system performance. Possible causes include failure of Microsoft Corporation to de-allocate memory in the program, or when bad code is executing an «infinite loop».
Error 70 Logic Error — A logic error triggers the wrong output even when the user has given valid input data. This happens when Microsoft Corporation’s source code causes a flaw in information handling.
Commonly, corrupt or missing Access Error 70 Permission Denied files cause these Microsoft Corporation errors, and are sometimes attributed to a current or past malware infection affecting Microsoft Access. Replacing your Microsoft Corporation file is generally a solution to fixing these issues. Moreover, as an overall cleanup and preventive measure, we recommend using a registry cleaner to cleanup any invalid file, Microsoft Corporation file extension, or registry key entries to prevent related error messages.
Typical Access Error 70 Permission Denied Errors
Access Error 70 Permission Denied Issues Related to Microsoft Access:
- «Access Error 70 Permission Denied Software Error.»
- «Access Error 70 Permission Denied not valid.»
- «Sorry, Access Error 70 Permission Denied encountered a problem.»
- «Cannot find Access Error 70 Permission Denied.»
- «Access Error 70 Permission Denied is missing.»
- «Start-up error in application: Access Error 70 Permission Denied.»
- «Can’t run Access Error 70 Permission Denied.»
- «Access Error 70 Permission Denied failed.»
- «Faulty Program Path: Access Error 70 Permission Denied.»
Microsoft Access-involved Access Error 70 Permission Denied issues happen during install, when Access Error 70 Permission Denied-related software is running, startup or shutdown, or during the Windows installation process. It’s important to note when Access Error 70 Permission Denied issues happen, as it helps troubleshoot Microsoft Access problems (and report to Microsoft Corporation).
Causes of Access Error 70 Permission Denied Errors
Malware infestation, invalid Microsoft Access registry entries, or missing / corrupt Access Error 70 Permission Denied files can create these Access Error 70 Permission Denied errors.
More specifically, these Access Error 70 Permission Denied errors can be caused by:
- Access Error 70 Permission Denied registry keys invalid / corrupted.
- Malware has infected Access Error 70 Permission Denied, creating corruption.
- Access Error 70 Permission Denied mistakenly deleted or maliciously by software unrelated to the Microsoft Access application.
- Another software in conflict with Microsoft Access, Access Error 70 Permission Denied, or shared references.
- Corrupted installation or download of Microsoft Access (Access Error 70 Permission Denied).
Product by Solvusoft
Download Now
WinThruster 2023 — Scan your PC for computer errors.
Compatible with Windows 11, 10, 8, 7, Vista, XP and 2000
Optional Offer for WinThruster by Solvusoft | EULA | Privacy Policy | Terms | Uninstall