I'm working with MS Access 2007 and I'm trying to migrate it to a Windows 10 computer. Up until now I have been working on Windows XP.
I use visual basic string functions (right left instr...) and lots of system calls (date, CreateObject("Scripting.FileSystemObject"), Application.FileSearch, FoundFileObj...) and when opening my database on a Windows 10 computer, it recognises neither string function names nor System calls.
When trying to close the database I get messages that utility.mda is missing.
So I figure that some of these functions are in utility.mda which is included in references in my visual basic editor on my XP Computer.
So I thought OK I download utility.mda on the Windows10 computer from the MS Access installation cd but the windows10 computer says utility.mda is protected and I can't download it.
Can anyone help? Any ideas how to fix this problem?
Thank you!
It's probably a reference problem.
Check this Microsoft guide.
Another guide: Link
Related
I'm on Windows 7 32 bit. When I open my access program, I get an error message as follows:
[Program Name] couldn't find file 'C:\Program Files\Microsoft Office\Office12\'. This files is required for startup.
The above listed directory however, is available - I can find it in Explorer, and I don't see why Access wouldn't be able to.
Note that the program I'm running was originally built in 2007, so it's old, but it was also built with compatibility with Access 2007 (supposedly).
I'm thinking maybe an Access profile issue, but I don't know where to start really.
Have you checked permissions for the folder? Perhaps your app is running as a non-privileged user. One thing to try is to run your app as Administrator.
I have recently installed a compiled Access application on a Windows 8.1 machine running Office 2013, and forms using treeview don't seem to be working. I get the error:
Object or class does not support this set of events.
Point is: You can no longer operate TreeView in 64 bit Office.
I solved my own problem with the following steps:
Deleted MSCOMCTL.OCX from \Windows\Syswow64
Opened the Access form that was giving me a problem, and Access reinstalled MSCOMCTL.OCX automatically.
Opened a command window with the "Run As Administrator" option
Navigated to \Windows\Syswow64
Ran regsvr32 /u MSCOMCTL.OCX
Ran regsvr32 MSCOMCTL.OCX
Reopened Access and it worked!
Note: You will need to do this in System32, NOT Syswow64 for 64-bit office. Dumb naming standard, I know.
#t_m , Thanks for your help!
I have an SSIS package that I use for a quick upload to a SQL database. I have recently moved to a different machine. New specs are Win 7 64bit and Office 2010 32bit. Had to have the 32 bit office in order for another program to run correctly. If I build/run the package in SQL Server Data Tools it completes. But if I try to run the solution from a batch script, I get the microsoft.ACE.oledb.12.0 is not registered error. I have searched many sites, and downloaded what I assume were the appropriate install packages to have the ACE driver.
I used a trick from one of the sites where you make a new text file, and rename it TEST.UDL. When I right click on the file, select properties, and go to the provider tab, Microsoft ACE is not listed. Is there another step to register the ACE driver that I am missing?
Thanks
I found that I was still executing the 64bit dtexec.exe, and had to rewrite my batch script to find the 32bit version.
Every time I try to run a Wizard in Access 2007 a dialog box pops up saying the following:
The database cannot be opened because the VBA project contained in it cannot be read. The database can be opened only if the VBA project is first deleted. Deleting the VBA project removes all code from modules, forms and reports. You should back up your database before attempting to open the database and dlete the VBA project.
To create a backup copy, click Cancel and then make a backup copy of your database. To open the database and delete the VBA project without creating a backup copy, click OK.
[OK] [Cancel] [Help]
(Yes, it's probably overkill to write out the entire message, but there it is.)
When I click [OK] Another dialog box pops up saying:
This feature isn't installed, or has been disabled.
...
However, I have installed every Access 2007 feature, including the wizards. In fact, earlier this Spring I used the wizards in another project and I haven't made any changes to my Office setup since then.
I have searched stackoverflow and the rest of the web but haven't come up with any solution to this problem. Does anybody have any ideas?
Thanks a lot.
--Knute
P.S. This also happens when I go to "Office Button"->"Access Options"->"Add-ins" and then try to select "Access Add-ins" in the "Manage:" combobox.
Update:
The problem happens with more than one Access database. I don't think it has anything to do with the actual Access database I'm working on because, as I added in my P.S. above, I see the same message when I try to manage my Access Add-ins through the Options panels (a feature that's not linked to any particular database). Does that make sense?
I uninstalled & reinstalled Access 2007 but did not uninstall & reinstall all of Office. I still have the problem. Any other ideas?
Does this happen with only one Access database file or multiple?
If multiple try re-installing Office/Access 2007.
If just one then check your references to see if there's anything wierd in there. Also try importing into a new MDB/ACCDB and/or a decompile. Decompile or how to reduce Microsoft Access MDB/MDE size and decrease start-up times
I finally found the solution to this. A poster on this www.utteraccess.com thread helped me figure it out. I had installed & uninstalled the 2010 Technical Preview awhile back and it apparently left an incompatible version of C:\Program Files\Common Files\Microsoft Shared\VBA\VBA6 on my machine. By deleting this folder, then restarting Access, I forced Office to run a repair installation. After the repair, my wizards started working again. Thanks for your suggestions, Tony.
I too was having this issue complete with the history of having uninstallaed Office 2010 Technical Preview. I am running a Lenovo X61 Tablet PC running Windows 7 64-bit mode. I found the broken VBA files here:
C:\Program Files (x86)\Common Files\Microsoft Shared\VBA\VBA6
Same solution: Delete the VBA6 directory.
The next time I ran Access 2007 it automatically went into its setup routine (a couple of minutes) and when it was done everything was working correctly.
Note: Uninstalling and re-installing Access 2007 did not solve the problem. I had to remove the bad directory as noted in bold above.
Anyone knows if it is possible to install Access 2003 standalone without the rest of the Office 2003? I seem not to locate my installation disks to test this out, but thought someone might have an answer...
I believe so, when you install Office and choose custom install, you can deselect everything except Access.
You can do a custom install and then deselect everything.
You will basically get all the MS Office run-time and shared components with only the Access application available to run.
Note: I don't use the access run-time any more, but do use it regularly for the Excel and/or Word applications.