Share
Report
30Product: Great Plains 10.0
OS: Windows 7 64-bit
I get this error whenever I open any GP window that has vba customizations. I have looked at the References list and nothing is showing as missing. The line that gets highlighted is the first line in the code. That line is always blank.
The odd thing about this is that if I delete my Windows Profile on the local machine, and then relogin with that same user name, the profile is recreated and I don't get this GP error for a while. It has come back twice now though.
I'm thinking that when I delete the user profile and then relogin, it's basically creating a new user on the machine. Running GP for the first time on this new user account rewires it to the the right one.
I develop the vba code on a 64-bit machine. Whenever we roll out new customizations to other machine, they get the new vba files. Most of the other machines are 32-bit.
If I start GP up on a new user account with the vba i developed on the 64-bit machine, i get this same error and can never resolve it.
However, if I start GP up on a new user account with the vba that was developed on a 32-bit machine, this error does not happen. Then I can go replace the 32-bit vba with the 64-bit vba and it still works, even though it did not work when the 64-bit is in there the first time GP runs.
Knowing that, I'm sure the problem lies somewhere in a file path or registry path: i.e. Program Files (x86) for filepaths or WOW6432Node in registry. 32-bit machines do not have those two and if developed on a 64-bit machine there is probably some references to those.
This has been a thorn in my side for quite some time. I usually never asks questions in a forum but this has been a killer. I would appreciate it if someone can help out. I know it sounds confusing, and it is. If I lack specifics, I apologize but I will add them on request.
*This post is locked for comments
All responses (
Answers (
