Microsoft Visual Basic - Run-time error '70': Permission denied

(0) Share

Report

Posted on by Ian Grieve

22,784

I have an odd problem at the moment. In the last few weeks I have started to get the above error on my development box when modifying a form or report by adding in an ADO connection.

The error appears on the line:
Set mobjConn = UserInfoGet.CreateADOConnection
I can use UserInfoGet to get the IntercompanyID or other values; if I move the code to the client's system the VBA works without problem. It only errors on my development box.

*This post is locked for comments

I have the same question (0)

All responses (13)

Answers (0)

Community Member on at

Like (0)

Report

Ian,

Looks like this is unresolvable for Windows 8! Have you been able to find a solution for this?

Was this reply helpful? Yes No
Ian Grieve 22,784 on at

Like (0)

Report

No, I have not been able to resolve the problem. I'm sure this did work until fairly recently, but not sure of exactly when.

I am still investigating as I need a fix for myself, but also any client who has customisations and may be looking to upgrade (assuming Windows 8 is the problem)

Was this reply helpful? Yes No
Lisa at AonC.com 921 Super User 2025 Season 2 on at

Like (0)

Report

I too am running into this for a client who upgraded from GP 2010 to GP 2015 ... I am not able to get the code to run on the local Windows 7 machine nor Windows 2012, even though all the references seem to be in place and the code is just a simple SELECT statement. The DLL is locked down and I haven't found a way to change the permissions on it. I too will keep searching!

Was this reply helpful? Yes No
Harold Worby 1,331 on at

Like (0)

Report

Try using the fully qualified name VBADynamics.UserInfoGet.CreateADOConnection

and check the VBA project's references.

You need the 'Microsoft Dynamics GP VBA xx.00 Library' for your version of GP xx.00

Was this reply helpful? Yes No
Lisa at AonC.com 921 Super User 2025 Season 2 on at

Like (0)

Report

Thank you for the suggestion ... Unfortunately it isn't working in my situation.

I changed "Set cn = UserInfoGet.CreateADOConnection" to

"Set cn = VBADynamics.UserInfoGet.CreateADOConnection"

Same error.

I do have a reference to Microsoft Dynamics GP VBA 14.00 Type Library. However, GP 2010 is also on the machine and the reference Microsoft Dynamics GP VBA 11.00 Type Library is available but not marked.

I'm going to check with the client to see if GP 2010 can be uninstalled just in case there is a conflict.

I'm interested in any other advice you may have!

Lisa

Was this reply helpful? Yes No
Matt Connor 65 on at

Like (0)

Report

Hi

It seems that a GP 2015 install breaks UserInfoGet.CreateADOConnection on ALL installed versions of GP. Must be one of the shared DLLs?

Matt

Was this reply helpful? Yes No
kjjson on at

Like (0)

Report

I am having the same issue on a GP 2015 install. Is there a workaround for this or another option to do this other than the UserInfoGet.CreateADOConnection?

Thanks,

Kevin

Was this reply helpful? Yes No
Matt Connor 65 on at

Like (0)

Report

Hi Kevin

The only workaround I've found so far is to use Windows authentication but it's not exactly a great solution. We need a fix from Microsoft really...

M.

Was this reply helpful? Yes No
Tim Foster 8,515 on at

Like (0)

Report

Have you filed an incident with support yet?

Is there a defect number to reference?

Tim

Was this reply helpful? Yes No
Suggested answer

Steven Vallarian 394 on at

Like (1)

Report

Cross-posting tammy's reply from partner support:

Hi All,

Thank you for the questions. This is a known issue with the DLLs installed as a part of the GP2015 Dexterity Shared Components. We are working to have this addressed in a tax release to be shipped later this month.

One thing to note is that once you install the GP2015 Dexterity Shared Components, you will get the error in both GP2013 and GP2015, if running/testing both on a single box. In order to get your GP2013 up and running again, uninstall the Dexterity Shared Components for BOTH GP2013 and GP2015; then reinstall the Dexterity Shared Components for GP2013 only.

Thank you,
Tammy Torgerson

Was this reply helpful? Yes No