Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Error when printing using the AccpacOE1100UICtrl

Status
Not open for further replies.

bryan1207

Programmer
Mar 7, 2018
28
PH
Is anyone encounter this issue? We created a custom screen using VB6 for Order Entry. But when we Post > (Select Serial/Lot Numbers) > Print. Got an error.
Capture_tbufmd.jpg
 
Copy the a4wcrInterop.dll to the folder where your custom executable resides.
 
@Djangman, I already copied the a4wcrInterop.dll from SAGE runtime to the executable. But still got the error. Also when debugging from VB6, the solution auto close when doing that print. Any advice? Thank you!
 
Try compiling the app and running the app, itself. Sometimes the VB environment introduces errors and odd behaviours that only appear when debugging.
 
Otherwise try turning on the REPCMD option in the registry to T and see if that helps to figure out what the issue is. Good luck!
 
@DjangMan, what do you mean REPCMD? It doesn't allow me to add the a4wcrInterop.dll from VB6 reference. How to do that?
 
If you find this registry key (could be under syswow64 as well):

HKEY_LOCAL_MACHINE\SOFTWARE\ACCPAC International, Inc.\ACCPAC\Debug\Repcmd

and give it a string value of

T

and then print you'll see a bunch of diagnostic messages appear. That might help.

You don't add a reference to the a4wcrInterop.dll in VB6 - you just copy it to the folder where your .exe file resides. Sometimes you have to compile the program and run the .exe to do your debugging because sometimes you get odd issues in the VB IDE.
 
I don't see any registry for: "HKEY_LOCAL_MACHINE\SOFTWARE\ACCPAC International, Inc.\ACCPAC\Debug\Repcmd"

Still having the error even I copy the a4wcrInterop.dll in the folder where your .exe file resides.

Also found this on my event viewer:

Faulting application name: VB6.EXE, version: 6.0.81.76, time stamp: 0x3592011f
Faulting module name: A4WAPI.dll, version: 6.7.0.0, time stamp: 0x5d5b9629
Exception code: 0xc000041d
Fault offset: 0x0006b986
Faulting process id: 0x5da8
Faulting application start time: 0x01d5a33b82478154
Faulting application path: C:\Program Files (x86)\Microsoft Visual Studio\VB98\VB6.EXE
Faulting module path: D:\SAGE\Sage 300\RUNTIME\A4WAPI.dll
Report Id: 631c8e10-969d-4470-9f3f-8e03192c617a
Faulting package full name:
Faulting package-relative application ID:
 
You need to create the registry key.

Sage 300 Certified Consultant
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top