1. Home
  2. Point-Of-Sale Software
  3. QSRules Custom Hook DLL Error

QSRules Custom Hook DLL Error

Hello: I have created two dll using QSRules and Hooks. The first dll uses the PrintReceipt Hook and records the transactionNumber and saves it to a session variable. The next dll is fired after the InitializeTransaction hook and successfully captures the session variable. A form is opened by the second dll and then the user closes the form. After the second dll end, I get two errors. The first is the "r6025 - pure virtual function call error" the second is the 'ciceroUI..." error. Am I handling the second dll incorrectly? Is there something I need to do to close the form? The POS crashes after the errors. Thanks, Rob

Reply to
Rob
Loading thread data ...

What development environment & language are you using? I'm almost positive that RMS has no clue what a pure virtual function call is, so I suspect that you've got a problem in your form itself. You might get a better response to this in the development language specific news group. Just make sure that you let them know that your application is being activated through COM Interop.

Glenn Adams Tiber Creek C> Hello:

Reply to
Glenn Adams [MVP - Retail Mgmt]

Start with Microsoft.Public.VB.General.Discussion

Or just google the error messages. I'm pretty sure they are not originating from RMS.

I was really expecting you to say you were using c# or maybe vb.net. Not sure how you're getting those errors in VB6 - maybe a bad install of a control used on your form?

Make sure you are trapping errors (On Error GoTo myErrorHandler...). You can run your project in the VB Development environment and get RMS to activate the dll in the debugger - this lets you step through your code and see which line is causing the error. You shouldn't have to do anything special to close your form, but you may be using object that need to be closed...

Glenn Adams Tiber Creek C> Thanks Glenn:

Reply to
Glenn Adams [MVP - Retail Mgmt]

BeanSmart website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.