Error when Trying to Export a Form with VBA through Customization Maintenance

(0) Share

Report

Posted on by Don Craig

280

Good Afternoon,

I have created a modification on the RM_Customer_Address. When I try to export this screen to create a package file I am receiving the following error message:

RM_Customer_Address Modified Form with VBA Procedure " not found.

I have checked the web and I have not been able to locate any information on this error message.

Your help with this would be greatly appreciated.

Thanks

Don

*This post is locked for comments

I have the same question (0)

All responses (5)

Answers (0)

Harold Worby 1,331 on at

Like (0)

Report

Be sure you don't have debug messages enabled.

Was this reply helpful? Yes No
Don Craig 280 on at

Like (0)

Report

Thank you for your reply. I have verified that the debug is not enabled and I have been able to verify that I have been able to export other Windows that have VBA attached to them.

I am still at a loss as to why this window is causing a problem.

thanks

Don

Was this reply helpful? Yes No
L Vail 65,271 on at

Like (0)

Report

Hi Don,

If you remove the .vba file, does it export properly?

Leslie

Was this reply helpful? Yes No
Don Craig 280 on at

Like (0)

Report

Good Morning Leslie,

Thank you for your reply. I found that issue is due to a problem with the third party dictionary it was found that any forms that we modified within this dictionary will not export due to the error that I received the first time. I have contacted the vendor to look at the issue.

In the mean time I have been able to copy the vba and the forms dictionary to the other workstations without a problem.

Thanks

Don

Was this reply helpful? Yes No
Derek Albaugh on at

Like (0)

Report

Hello Don,

We haven't seen this type of error very commonly, but based on what you stated, my thinking is that the code for the RM_Customer_Address modified form is corrupt in some way.

What you can try is to go into VB Editor and copy all the VBA code for this modified form, then delete it from VBA and then attempt to export it out into a package file.

If you an do that, then you could add the VBA code back as needed.

Thanks,

Was this reply helpful? Yes No