It works great in my development environment, but in a test situation it fails. I made sure in the test environment that the dll is registered.
Any ideas or help?
thanks, Nick
Atempt to process COM object VerifyCust.cVerifyCust failed.
Jul 14, 2005
12 Replies
How about seeing the code and supplying how it's setup in the registry and when it's supposed to execute?
Kevin
Public Function Process(Session As Object) As Boolean
Process = False ConnectToDB Process = StartResearch If Process = True Then LoadWeightingFactor ComputeCheckDigit UpdateDatabase End If dbAccess.CloseDb
End Function
Which registry entries did you want to see?
"Fisher" wrote:
"ClothingStore" ha scritto nel messaggio news: snipped-for-privacy@microsoft.com...
Same environment (components) ? And same QSRules version?
antonio
Do you can post your project for verify?
Antonio
What development environment are you using?
VB.Net? Does the target system have the .Net Framework installed?
VB6? You need to create an installer package using the Package & Deployment Wizard - a VB project has dependencies on the VB Runtime engine among other things - the PD wizard will get all of the dependencies installed & Registered on the target system. Just copying the .dll over is not enough.
Yeah, the deployment wizard should have gotten any dependencies. Some one mentioned earlier that you should check the RMS versions on your dev and test environments. Also, you should remove any reference to QSRules.dll before you build your project - just reference everything as an object.
You might try writ> Hello Glenn,
I wanted to say thank you and log my problems, in case someone else runs into these same problems. The problem is I had more than one problem so it was hard to diagnose, but here were the things that might help other in the future.
1) Make sure you do not have QSRules.dll referenced in your project and use an objeect as Glenn had stated. 2) Put message boxes in your code because this generic error that pops up about the attempt to process com object could be working just find, but bombing on a piece of code it has encountered that it does not like. 3) If all else fails you can copy your dll to the winnt\system32 directory and regiter your dll for example regsvr32 verifycust.dll. 4) You must create a VB deployment package to install your dll. If you are making a database connection you might even have to include or reference a ADO like 2.7, because that will include the mdac with the install that might be needed with your project. Be careful as usual when installing mdac, this is a last resort type of thing.Thanks everyone you are awesome.
"Glenn Adams" wrote:
Just a comment,
You don't necessarily have to put your DLL in System32, they can be anywhere (atleast I think anywhere, maybe RMS will only recognize it if it's in a system path or under the RMS directory? I'm just guessing.) I usually put my DLL's in the RMS Add-Ins directory, and then use regsvr32 on them.
I having same problem. But I solve the issue already:
This how you can solve the problem
1.) Check the version of the RMS on both side. your development PC and Test PC. Both should have the same version. 2.) Compile your DLL on your Development PC. 3.) Regsvr32 "location of the DLL file"then it will going to work fine.
I having a lot of trouble finding a solution but i found out that i have different version on my development pc and Cashier PC. so I tried to both upgrade my version to RMS 1.3. Then I complie the DLL and run the regsvr32 or register my dll to the cashier PC and it work.
H> It works great in my development environment, but in a test situation it
Join the Discussion
Have something to add? Share your thoughts — no account required.
Didn't find your answer?
Ask the community — no account required