Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Ok firstly, I found that there are a number of issues with .net COM dlls interaction with VBA. </p> <p>Firstly, configuring them in with .net via attributes, so they correctly configured in the registry is important. Make sure the Dll project has been marked Register for COM interop.</p> <p>Secondly, if you using an MSI project, ensure that the software has been marked "Install all users". MSI projects do a very poor job of removing registry entries, so if you muck up MSI installs, .net version etc your server ends up with "bad registry entries". I end up using regasm.exe to correctly register the component. I've ended up moving to WIX project installs.</p> <p>Thirdly, you need to ensure that the registry entries are "machine/global" wide, for terminal server, as each users will be running a potentially different set of "registry" entries. If you have setup the namespaces correctly, you should be able to do early binding in VBA, rather than the riskier late binding "CreateObject" calls. Just make sure the VBA checks for "broken references" during startup.</p> <p>Forth, I use a very clean VM to test my installations and registry entries, with the help of MS Office VBA References, to confirm the COM parts have registered correctly, so "CreateObject" calls are not going to fail.</p> <p>Fifth, watch out for the x86/x64 issues with Terminal server and the explicit version of office your running (Office 2010 x64 in particular). You may have to use the compiler flags /86 explicitly if the server is a x64 (Any CPU can be very bad for VBA .net COM objects).</p> <p>Sixth, Watch out for the way you raise exceptions from .net to COM. Have a look at System.Runtime.InteropServices.COMException for the correct approach.</p> <pre><code>From cmd c: cd C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727{or the edition your using} COPY "\\Distribution Share\{YourCompany}\{Software}\{Edition}\{.net Com DLL name}.dll" "C:\Program Files\{YourCompany}\{Software}\{.net Com DLL name}.dll" Regasm.exe "C:\Program Files\{YourCompany}\{Software}\{.net Com DLL name}.dll" /u Regasm.exe "C:\Program Files\{YourCompany}\{Software}\{.net Com DLL name}.dll" /regfile:"C:\Program Files\{YourCompany}\{Software}\{.net Com DLL name}.reg" /codebase cd C:\WINDOWS\System32\ Regedit.exe /s "C:\Program Files\{YourCompany}\{Software}\{.net Com DLL name}.reg" </code></pre> <p>I then have a really close look at the registry files that are generated to ensure they are in the correct registry hive.</p>
    singulars
    1. This table or related slice is empty.
    1. POInstalling com-enabled .net assembly onto Windows Terminal Server
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USJamie Clayton
    1. USJamie Clayton
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTBountyClose
    1. COThanks for mentioning System.Runtime.InteropServices.COMException
      singulars
      1. PO
      1. USDerek Tomes
    2. CO1. Yes, I did that. 2. No, I don't use MSI. Just xcopy deployment of the whole project directory and tried to register it manually/with VS help 3. How exactly do I "ensure " it? And no, early binding is not an option. 4. I do not believe 64/32 conundrum is at fault here - it runs perfectly if run in the same user acc it was registered. Also, see update
      singulars
      1. PO
      1. USAlexVhr
    3. COMy fall back for these issues is to open MS Access/Excel and create a VBA module. I then goto "references" to confirm the .net COM dll reference is correctly available in the list. Sometimes you have to browse to the *.tlb file that's created (NOT THE DLL). If that works correctly in VBA, then CreateObject("Namespace.Class") should work in whatever environment you want, See http://social.msdn.microsoft.com/Forums/pl/isvvba/thread/3fee8d3d-3a65-4d03-b4c1-a9b55ece1ffc for a quick overview of the technique.
      singulars
      1. PO
      1. USJamie Clayton
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload