I have to work with Visual Foxpro 9.0 to access the PDM Ent. Vault. On Windows XP, this has not been a problem using the CreateObject function to create an instance of the vault and work with it; no problems. Now that we have moved to Windows 7, this will no longer work. I keep getting a 1733 error message when creating the vault instance, i.e. loVault = CreateObject("ConisioLib.EdmVault"). Has the "ConisioLib.EdmVault" name changed or something with Windows 7? Is there a COM restriction preventing use of this method in W7? Any help or information on this would be greatly appreciated.
Don
SolidworksApi macros
Hi Don.
I'm not really familiar with Visual Foxpro, but it sounds like you might have a missing reference somewhere. Did you include the latest references from your EPDM installation in you environment?
Yes, all latest references are set. On Windows XP, i can find in the registry the ConisioLib.EdmVault object. It is not in the Windows 7 registry. I can't find any other installation package to add it.
Thanks,
Don
One more question : do you use 32bit or 64bit operating system?
I use Interop.Edmlib.dll for EPDM 2009 / 2010 and later
Not sure what you are developing for? Is it a standalone application connection to a vault or an addin for enterprise...
I use this dll for standalone / addin applications
But then... I don't use VFP. I use Visual Studio Express 2010. I've found no limitations in the express versions that I can't do without.
I have not found it necessary to use the createObject() command (although this could be VFP specific)
Hope this helps
I am on a 32 bit system.
The application I am working with is a legacy system that I have to keep running for a few more years.
Just pulling at straws, I ran regsvr32 on the EdmInterface.dll file this morning and now it works as before. I don't know why the installation of PDMWE would not have fully registered this, but it works. Now I have to run this on all machines.
Thanks for your responses anyway!
Regards,
Don
It's a pleasure.
In my experience, if dll's don't register properly it could be that the anti-virus was interfering with the registration process. Happened quite a lot with a number of clients. We check that as our first resort. Especially after software miraculously stops working all of a sudden.
Or it could be a firewall / overactive group policies.
Anyway... glad you got sorted