![]() | |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
I have some code in A2010 that interfaces with SolidWorks EPDM api using early binding. Some user don't have EPDM installed so I would like to use late binder, currently I have to maintain 2 version of the FE. The problem is EPDM is a Windows File Explore add-on and has no separate user interface to call using something like CreateObject("Outlook.Application"). How can I late bind with an add-on application? |
#3
| |||
| |||
|
|
I have some code in A2010 that interfaces with SolidWorks EPDM api using early binding. Some user don't have EPDM installed so I would like to use late binder, currently I have to maintain 2 version of the FE. The problem is EPDM is a Windows File Explore add-on and has no separate user interface to call using something like CreateObject("Outlook.Application"). How can I late bind with an add-on application? |
#4
| |||
| |||
|
|
"ron paii" <none (AT) nospam (DOT) com> wrote in message news:j4q77f$jjk$1 (AT) dont-email (DOT) me... I have some code in A2010 that interfaces with SolidWorks EPDM api using early binding. Some user don't have EPDM installed so I would like to use late binder, currently I have to maintain 2 version of the FE. The problem is EPDM is a Windows File Explore add-on and has no separate user interface to call using something like CreateObject("Outlook.Application"). How can I late bind with an add-on application? Late binding will not work if the software is not installed at all. You cannot create a connection to software that just isn't there. The difference between early and late binding is speed and versioning. The difference in code is like this: Early Binding: ' Declare the object as an early-bound object Dim objAccess As Access.Application Set objAccess = CreateObject("Access.Application") ' The Visible property is called objAccess.Visible = True Late Binding: ' Declare the object as a late-bound object Dim objAccess As Object Set objAccess = CreateObject("Access.Application") ' The Visible property is called objAccess.Visible = True -- Arvin Meyer, MCP, MVP http://www.datastrat.com http://www.accessmvp.com http://access.mvps.org Co-author: "Access Solutions", published by Wiley |
#5
| |||
| |||
|
|
I have some code in A2010 that interfaces with SolidWorks EPDM api using early binding. Some user don't have EPDM installed so I would like to use late binder, currently I have to maintain 2 version of the FE. The problem is EPDM is a Windows File Explore add-on and has no separate user interface to call using something like CreateObject("Outlook.Application"). How can I late bind with an add-on application? |
#6
| |||
| |||
|
|
On Wed, 14 Sep 2011 07:38:06 -0500, "ron paii" <none (AT) nospam (DOT) com wrote: I have some code in A2010 that interfaces with SolidWorks EPDM api using early binding. Some user don't have EPDM installed so I would like to use late binder, currently I have to maintain 2 version of the FE. The problem is EPDM is a Windows File Explore add-on and has no separate user interface to call using something like CreateObject("Outlook.Application"). How can I late bind with an add-on application? Can you post some sample code showing how you start using it? Tony -- Tony Toews, Microsoft Access MVP Tony's Main MS Access pages - http://www.granite.ab.ca/accsmstr.htm Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/ For a convenient utility to keep your users FEs and other files updated see http://www.autofeupdater.com/ |
#7
| |||
| |||
|
| "Tony Toews" <ttoews (AT) telusplanet (DOT) net> wrote in message news:m9227710ts4td27kqkajuo61pu6eplvqsj (AT) 4ax (DOT) com... On Wed, 14 Sep 2011 07:38:06 -0500, "ron paii" <none (AT) nospam (DOT) com wrote: I have some code in A2010 that interfaces with SolidWorks EPDM api using early binding. Some user don't have EPDM installed so I would like to use late binder, currently I have to maintain 2 version of the FE. The problem is EPDM is a Windows File Explore add-on and has no separate user interface to call using something like CreateObject("Outlook.Application"). How can I late bind with an add-on application? Can you post some sample code showing how you start using it? Tony -- Tony Toews, Microsoft Access MVP Tony's Main MS Access pages - http://www.granite.ab.ca/accsmstr.htm Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/ For a convenient utility to keep your users FEs and other files updated see http://www.autofeupdater.com/ This is the function I use to login to EPDM '------------------- ' Opens the Vault and hold open in static var ' Keep ref to vault open for improved speed ' ' Return Reference to the vault ' Private Function EPDM_GetVault() As EdmVault5 Static m_Vault As IEdmVault12 ' Open vault If m_Vault Is Nothing Then Set m_Vault = New EdmVault5 ' Loginto vault, using current user login Call m_Vault.LoginAuto("SWVault", "None"), _ GetAccesshWnd()) Else If Not m_Vault.IsLoggedIn Then ' Loginto vault, using current user login Call m_Vault.LoginAuto("SWVault", "None"), GetAccesshWnd()) End If End If Set EPDM_GetVault = m_Vault ' Return reference to Vault Exit Function End Function . |
#8
| |||
| |||
|
|
Late binding will not work if the software is not installed at all. You cannot create a connection to software that just isn't there. The difference between early and late binding is speed and versioning. |
#9
| |||
| |||
|
|
I have some code in A2010 that interfaces with SolidWorks EPDM api using early binding. |
#10
| |||
| |||
|
|
"ron paii" <none (AT) nospam (DOT) com> wrote in news:j4q77f$jjk$1 (AT) dont-email (DOT) me: I have some code in A2010 that interfaces with SolidWorks EPDM api using early binding. Basically, you need to find the name of the component that you need to initialize with CreateObject. You have to poke around the registry for this. I would start by looking up the name of the file in the early binding reference, and then search the registry for that. -- David W. Fenton http://www.dfenton.com/ contact via website only http://www.dfenton.com/DFA/ |
![]() |
| Thread Tools | |
| Display Modes | |
| |