I have an Access application that VBA references to Microsoft ActiveX Data Objects but I find that the path to the msado28.tlb type library is wrong (point to a network location!!!).
I found a PC that it does not have problem and the correct path is C:\Program Files (x86)\Common Files\System\ado\msado28.tlb.
I tried to point to this location but nothing happened!!
The pc's have Windows 7.
Related
I am very new to visual studio and i am building a data entry app in it using visual studio connected to Microsoft access database (VB.NET language).
But i am getting error during initial debug to check on the path like below:
System.Data.OleDb.OleDbException: ''C:\Users\ramadasr\source\repos\Test2\bin\Debug\Database\Trialdatabase.accdb' is not a valid path. Make sure that the path name is spelled correctly and that you are connected to the server on which the file resides.
And I have entered the app.config data correctly like below:
connectionString="Provider=Microsoft.ACE.OLEDB.12.0;Data Source=|DataDirectory|\database\Trialdatabase.accdb"
And actual folder location is this: C:\Users\ramadasr\source\repos\Test2
Please help me how to correct this , i have attached some images also for your reference.
2 choices
external location - keep your DB in a specific folder, like c:\myDB, This way, you just add this folder into your app.config and run with that
relative location - add your db file as item of your project. Set in properties for this file - Content and CopyAlways. In the app.config have the relative path.
Another variant - add DB file to your project as link from any location. And use same settings as #2
I have written a VBA macro in Excel that references a .dll library (COM-interface) located in a UNC path (\\SERVERNAME\FOLDER).
Unfortunately my company started blocking the use of dll-files in "untrusted locations" in Office, which includes all UNC paths (using Sophos).
Is there any easy way that I can create a .dll that simply references/redirects to the original .dll?
I am curious to modify the .dll file for VBA based on these suggestions to get a custom color scheme.
When I inspect references in the VBA Editor I see a reference to
C:\Program Files\Common Files\Microsoft Shared\VBA\VBA7.1\VBE7.dll
Problem:
Using File Explorer or Chrome, it appears the VBA folder does not exist. There is no VBA folder at
C:\Program Files\Common Files\Microsoft Shared
Image showing VBA folder does not exist
In my File Explorer options I have configured to show hidden and protected folders. I believe it should be showing based on my settings.
My File Explorer Settings 1/2
My File Explorer Settings 2/2
How can I find the file at my destination, in order to backup and modify it? Since VBA does work on my machine, I am confident it does exist.
If you have 32 bit office it would not be there but at C:\Program Files (x86)\Common Files\Microsoft Shared\VBA\VBA7.1\VBE7.dll.
I'm using Office 2019 (Microsoft® Excel® for Microsoft 365 MSO (16.0.14326.20850) 32-bit
After running an extensive search for that dll on my entire PC, I found it here:
c:\Program Files (x86)\Microsoft Office\root\vfs\ProgramFilesCommonX86\Microsoft Shared\VBA\VBA7.1\
I have exe file and, that uses my own .dll library. When I launch exe file I get the error
The procedure entry point for SomeFunction could not be located in the
dynamic link library mylib.dll.
How can I fix this problem ? Is this possible to change the header in .dll using CFF Explorer or Windbg ?
I am using Scott Mitchell's textBox Characters and Words counter control, i downloaded it from the website https://web.archive.org/web/20211020202742/https://www.4guysfromrolla.com/ and unzipped it to my desktop. then in VWD Express 2008, i created a new tab in the Toolbox, i chose the *.dll from the unzipped folder, i used the control, all is fine (try it, i recommend it) but when i backed up my code, copied the site, and tried to run it on another computer, i got a bunch of error all indicating that its looking for the dll file on my desktop, but when i checked under my bin folder in my website directory, the dll is there...
Help Plz...
If you view the properties of the reference you'll probably find that the path to the reference is incorrect.
I have often found that the quickest way of fixing the problem is to open the project file with notepad and correct the path to the reference.