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.
Related
I have a handful of MS Access 2010 databases that are used to keep track of various things for my group. Each Database has a dedicated back end and each user has a local copy of the front end (*.accdr) and 2010 access runtime. Only three of us have full versions of Access. Each DB has up to 6 users and some users have multiple DB's they use regularly. One user in particular has multiple problems with these DB's. One of them has a form where you put criteria in some text boxes, click a button and another form opens displaying data. Everyone else has this perform seamlessly. On hers, it throws up a dialog box asking for the criteria a second time. This is pretty universal across the DB's that she uses. On another DB, Clicking a button triggers a macro to export of a query to a MS Excel spreadsheet. This will generate an unspecified runtime error and then shutdown the entire frontend. Again, this works fine for other users.
I have systematically gone through and tried each DB from each user's computer. I have checked and rechecked the source *.accdb files I generate the front ends from. The problem seems to exist only on this user's computer.
She does have a full copy of Access 2010, but she doesn't ever use it. She also has 2010 runtime. All of our machines are connected by Ethernet to the server where the Back ends are stored.
I would expect the front end to behave the same way on her machine without unexpected pop ups or runtime errors since it behaves as it should on every other user's machine. I don't know what to look for now, and I am not inclined to throw up my hands and blame a bad setup on her machine. Is there some logical steps I can take now, since IT support is one place no sane person in my office wants to do (bad for the blood pressure). Any help, advice, or even Mystical Incantations would be appreciated.
This is a common occurrence.
The HUGE MASSIVE tip-off is that the accDB works, but the accDE (pre-compiled) does not.
And the next HUGE MASSIVE tip-off is compiling the accDB to an accDE on that particular machine ALSO works.
The reason and problem for this is that the version of Access running on that machine does not match the save version that you are running on other machines. (Specific the machine used to compile the accDB into the accDE).
While of course you are running access 2010 on all machines, the problem is the SP update version (Service Pack(s) installed).
Keep in mind that the runtime is NOT updated by windows update.
Keep in mind that running the office SP update will NOT update the runtime (but this will only apply to runtime only machines).
So, on your dev computer? Well automatic updates can roll out a SP update to office 2010.
However, automatic windows updates NEVER update the access 2010 runtime. You must install the 2010 runtime SP updates manually. So with a mix of runtime and full editions?
Well, the machines with full edition will wind up with SP updates occurring (they over write the runtime on those machines). In fact, you can’t install both full and runtime on the same machine. The installer allows this, but it is a “fake” install, and installing the 2010 runtime on machines with full edition in fact does NOTHING!! (Well, it does create a “fake” entry in the list of programs installed – but it DOES NOT actually install the runtime, since it would overwrite the full edition that already exists on the machine).
On computers with the full edition, then installing the SP updates to office, or even allowing windows update to do this will NOW cause the 2010 version to be DIFFERENT then your developer machine.
The reason why the accDB works is because Access (even the runtime) will detect that the “sp version” is different, and re-compile the VBA on the fly. Even the stand alone runtime version is able to re-compile the source VBA code.
However, with an accDE?
The code is pre-compiled, and thus no on-the fly re-compile can occur. There is no source code. The accDE should and often MUST be run + consumed by the SAME sp update version.
To reduce, or all but eliminate this issue?
Well, on your dev machine, make sure the sp2, or sp3 update to office has been applied.
On the target computers? If they are runtime only, then you MUST install the sp2 or sp3 update to the access runtime. I cannot stress that you MUST download and install the SP2 or SP3 update for the access runtime. The office sp update WILL NOT work nor will it update the runtime version on runtime only machines.
Because of the above?
I recommend you download the 2010 runtime. Download the sp3 2010 runtime update, and “slip stream” the sp3 update INTO the 2010 runtime installer.
You can then provide the customer site (or your site) with a folder on the server with the runtime to install, and WHEN you install the runtime, then the sp3 update will be included in that install.
If you (or your IT department) does NOT know how to slipstream in the sp3 update, then simply ALWAYS have then install the 2010 runtime, and then ALWAYS install the sp3 update for the 2010 runtime.
Doing the above will eliminate the issue of the AccDE having been created and compiled with a different release version of access.
Last but not least?
No question you want to continue using a compiled accDE, since with the runtime, then any un-handled error with an accDB will not only spit out an error message, but shutdown the whole application.
So:
With accDE:
Errors NEVER re-set global or local variables.\
Errors will NEVER cause a shutdown of the runtime.
Even un-handled errors will NOT cause a shutdown of your application.
Un-handled errors will NEVER re-set local, or global variables they will ALWAYS no matter what retain their values for the duration of the appcation session.
With accDB and runtime:
Any un-handled error will blow out all local and global variables.
Any un-handled error will then shut down the runtime after display such errors.
Bottom line:
Using an accDE is thus vastly far more reliability then an accDB when using the runtime.
OK, First of all, thanks for all your suggestions in the comments. We figured a method to keep my user working, so I will put it here.
We reasoned that since the executable ran fine on multiple machines, there may have been some sort of unknow quirk in my users machine that was causing the issues. I started my re-making the front end in the normal way and pushing it out to just the one user. It failed just like before.
Since she had a full copy of Access 2010, we opened the source *.accdb file directly on her machine. That time, It worked just fine.
From there I went, possibly a little overboard. But it worked out.
I opened all the forms in design view. Double check for errors, then save each form in turn. After that, I did the same with the macros. Not making changes, but checking the work.
Next I ran a compact and repair, from the affected machine.
Then I used the affected machine to create a new front end executable.
Lo and Behold, it worked. The affected user now has a completely functional front end.
This is going to make updating the front end a pain in the keister moving forward, but at least now I know what will actually work.
Thank you for your help
We have a really old Microsoft Access tool that is currently using the 2007 runtime. I need to update the users to the 2010 runtime but they are located on separate buildings so physically uninstalling the old is not very practical. Does anyone know of a way to uninstall through the command line? I found this one for 2010 but it doesn't work for 2007
http://www.shouldiremoveit.com/Microsoft-Access-Runtime-2010-21278-program.aspx
After a little more digging I found the answer. Run MsiExex with the product GUID
MsiExec.exe /qn+ /X{90120000-001C-0409-0000-0000000FF1CE}
At work, we often create access applications to perform imports from certain files to the database.
We always create those mde files in access 2003.
Normally, people who run these applications have a full office (with access) installed and are able to run the .mde files.
For a new application we have a user that has an office 2010 installed, without access.
So we installed an access runtime version on their PC's so they would be able to open and use our mde file. Although we keep getting the "there is no object in this control" when we open the .mde file with the access RT version.
Anyone has an idea what is causing this issue ?
Kind regards,
When you build a runtime package you have to make sure all dll and other references are included so they get installed on the users machine. I would guess you are missing one of them. Do you know where to view references? If not make sure to open the VBE and look under tools/references. Remove any that aren't used. Then make sure any that are used are in your runtime package.
We fixed it by removing a Progress bar from the application. The libraries were not included in the runtime version neither by default in Windows. After removing it, the application ran perfectly fine on the RT editions of Access.
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.
I have a .NET application which uses an accdb file (MS Access 2007 format) as its database. To install this app on another machine I need to install the Access engine on that machine. Microsoft has this file: AccessDatabaseEngine.exe which includes the engine, but when extracted during installation, runs another .msi installer.
As you can guess, since this msi is run during the installation of another msi (my app's installer) the Access engine setup fails with error 1500: "Another installation is in progress. Finish that one before continuing this one..."
I found the Runtime for Access 2007 as well, and it does install the engine, but the Runtime package is again an msi installer which means I'm still having the same problem.
Any ideas to include the engine in my app's installer?
You probably want to have a look at this article: Adding Programs to Access 2007 Deployment Packages
The Access Developer Extensions offer a basic but functional installer that can take care of the general deployment scenarios.
The best think would be to build your own msi pack including needed access files. You could use a product like VERITAS Wininstall. You have this "Discover" method that allows you to build a fully operationial .msi file by (1) taking 2 snapshots of your system (one before the installation, one after) then (2) creating the .msi file corresponding to the installation process.
Anyway, I'd advise you to have multiple packs, one for Access, that can be installed with a "for all users" option when the computer joins your company's domain, one for your app. By doing so you will be able to distribute new versions of your app without redistributing Access, which takes a few mega of space as well as a few minutes of user's most precious time).
Sio if Microsoft already delivers an Access Runtime msi package, just keep it 'as is' and distribute it automatically on your network when a new machine joins the domain.
I wouldn't recommend WinInstall, we have it in my office and we have to keep calling them in to package stuff for us as it's so finiky to use. Some things they haven't been able to package at all. WISE Studio is better or a free alternative is AppDeploy whihc I have heard great things about.
I found this software called "Bootstrapper Manifest Generator" or BMG. It helps create a prerequisite package using an MSI or EXE installer file, and adds it to VS2008 Prerequisites dialog box in Setup and Deployment projects. Although it's not that user friendly, it does the job. It's on MSDN: code.msdn.microsoft.com/bmg
Thought it's good to save others from going through all the trouble.