By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
459,963 Members | 1,994 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 459,963 IT Pros & Developers. It's quick & easy.

Access 2007 Developer crashed can't get it to reinstall

100+
P: 462
I was running the developer on my program and it crashed. When I start access again the developer was gone. I went to the Microsoft website and download the developer extension again and installed it but the developer still doesn't show up. Any ideas what's wrong or how do I fix this.
Thanks
Jun 2 '15 #1

✓ answered by Seth Schrock

When I installed Office 2013 on top of Office 2010, it broke my developer addin as well. I have just created my own vbs scripts to take its place.

Share this Question
Share on Google+
8 Replies


zmbd
Expert Mod 5K+
P: 5,397
Try this first :
https://support.microsoft.com/en-us/kb/937998


IF that doesn't work, then go to the control panel > programs...
see if the extensions are listed there.

Depending on what happened you may have an orphaned installation listed that is preventing the reinstall. If it is listed see if there is a repair option, else, uninstall... last ditch that I know of is a drastic one so let us dig around for a little bit to see what else may turn up :/
Jun 3 '15 #2

100+
P: 462
I'm wondering if maybe because I installed office 2013 but am using Access 2007 that this could be causing a problem. I was having problems with outlook 2007 and thought maybe office 2013 would work for everything I'm doing, but when I found out the Access 2013 doesn't have a packaging section for deploying my program I decided to go back to Access 2007 until I found a way to package my program. If you thing that could be the case them I'll just try and find a way to package Access 2013.
Thanks
Jun 3 '15 #3

100+
P: 462
I thought maybe Office 2013 would let me not install Access but that's not the case. It's all or nothing.
Jun 3 '15 #4

zmbd
Expert Mod 5K+
P: 5,397
dual installations of Office versions causes many a headache...
MS Article: Install and use multiple versions of Office on the same PC

So it sounds like the drastic measure must be taken...
COMPLETELY UNINSTALL ALL OFFICE
Sorry

Follow the instructions in given in the link above, install ACC2007 and the developer's addin FIRST then install the newer version.

and this may not fix the issue either.

Maybe someone else will have a better solution.
Jun 3 '15 #5

Seth Schrock
Expert 2.5K+
P: 2,951
When I installed Office 2013 on top of Office 2010, it broke my developer addin as well. I have just created my own vbs scripts to take its place.
Jun 3 '15 #6

100+
P: 462
Seth, would you mind sharing your vbs script, I'm not very good at scripts and an example would be a big help in putting me on the right track.

Thanks
Jun 3 '15 #7

Seth Schrock
Expert 2.5K+
P: 2,951
There are three files. Database Packager.vbs is the one that you would run. Basically my idea is this. I store all of my databases on a server. I have a folder called Databases on this server and then a folder for each database project
Expand|Select|Wrap|Line Numbers
  1. \\Server\Database\
  2.     Loan Tracking\
  3.     Billing\
  4.     Key Log\
  5.     etc.
In each folder, I have the following structure:
Expand|Select|Wrap|Line Numbers
  1. \Loan Tracking\
  2.     Backups\
  3.     Full Database\
  4.     Installation_Files\
  5.     Supporting_Documents\
So I develope my databases stored in the Full Database folder and have all my database versions stored in that. To publish my database, I copy the version I want published to the Installation_Files folder. It is then this copy that gets copied to each computer. I also have my installation scripts stored in the Installation_Files folder. I got tired of going through those scripts and changing everything to work for each database, so I created these scripts to help with that. When I created these scripts, I used DSNs when connecting to SQL Server backend. Now I just use DSN-less connections.

All that as a background for how my scripts work. It will ask you a series of questions to build the scripts.

1. Enter the location where the installation files will be put
It is asking for the "Loan Tracking" level folder.

2. What is the program's name?
This is what you want to call the program

3. How many DSNs need created?
If you use DSN-less connections or you are connecting to an Access BE, then put 0. Otherwise you can put however many you need. Most of mine would need two. If you need them, then it will ask for the DSN Name, Server Name, and Database Name and will create the VBS script to add those DSNs to the registry.

4. Install Location:
This is asking where you want the database to be installed on each local computer. I always install it on the C:\ drive, so an example would be C:\Loan Tracking

5. Icon File name with location from database root folder:
I always put my icon file in the Supporting_Documents level folder. Example Supporting_Documents\icon.ico

6. Number of Files needed for an x64 installation:
7. Number of Files needed for an x86 installation:
If you need other files ran on each computer when you install it then, you can put those files in the appropriate folders that get created in this script. If you put 1 or more, it will ask you for those file names.

I think that is about it. You will need to change the file location in line 155 to match where you download these files. You will also need to change the email settings in the InstallScriptSource.vbs file to match your needs.

Let me know if you have any trouble.
Attached Files
File Type: zip Database Packager.zip (3.0 KB, 68 views)
Jun 4 '15 #8

100+
P: 462
Thank you very much.
Jun 4 '15 #9

Post your reply

Sign in to post your reply or Sign up for a free account.