Search for that CLSID in the registry and see which DLL it's pointing to - maybe you haven't
packaged all dependencies? If it's a COM interop object then have you asked it to be 'copied
locally' for your project thus ensuring it gets packaged?
Chris.
"Wayne Wengert" <wa***************@wengert.com> wrote in message
news:ue**************@TK2MSFTNGP14.phx.gbl...
I copied the CLSID incorrectly - it should be:
00000602-0000-0010-8000-00AA006D2EAA
Sorry about that.
Wayne
"Wayne Wengert" <wa***************@wengert.com> wrote in message
news:Of**************@tk2msftngp13.phx.gbl...
I have a VB.NET Windows app which gives the users the option to open an
existing Access DB or create a new one. I used VSNET 2003
Package/Deployment to create an install package. I've had 3 people test it and on one machine
the user gets an error message:
"COM object with CLSID (0000602-0000-0010-00AA006D2EA4) is either not
valid or not registered"
Has anyone seen this type of problem and/or have ideas on how to debug it?
TIA
Wayne
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (
http://www.grisoft.com).
Version: 6.0.777 / Virus Database: 524 - Release Date: 14/10/2004