If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
|
#1
|
|||
|
|||
Access Developer Extensions and Office 12
I have an Access database that was designed in Access 2003. I also have the
Access Developer Extensions (2003 – 11.0.5622). I just recently installed Office 12 on my laptop but I have Office 11 on my desktop. I tried to use the Packaging Wizard on my laptop but received the following error message: - dataroot - Error AppNamePackage Wizard/AppName AppVersion11.0.5622/AppVersion AppInstallLocationC:\Program Files\Microsoft Office\ADE11\/AppInstallLocation AccessVersion12.0/AccessVersion AccessBuild4518/AccessBuild AppFileNameC:\Program Files\Microsoft Office\ADE11\WZADE.MDE/AppFileName IsAddInFalse/IsAddIn FileTypeMDE/FileType ModNameForm_frmWizardShell/ModName ProcNameForm_Load/ProcName ErrorNumber5/ErrorNumber DescriptionInvalid procedure call or argument/Description Time2009-08-06T11:28:20/Time /Error /dataroot Three questions: Does this mean the Developer Extensions will not work with Office 12, and that I cannot create a package on my laptop? Does this mean that if I used the Packaging Wizard on my desktop with Office 11 (also on my desktop) that the ultimate package could not be installed on a computer that had Office 12 on it? Has there been another Developer Extensions issued that I don’t know about, and if so, how do I acquire it? Thank you for any insight you can provide. It would be so nice if these could all play well together... Mary |
#2
|
|||
|
|||
Access Developer Extensions and Office 12
Hi,
you can download the developers extensions for Access 2007 free from the MSDN site. For more info check out http://msdn.microsoft.com/en-us/library/bb501030.aspx -- Kind regards Noëlla "sweeneysmsm" wrote: I have an Access database that was designed in Access 2003. I also have the Access Developer Extensions (2003 – 11.0.5622). I just recently installed Office 12 on my laptop but I have Office 11 on my desktop. I tried to use the Packaging Wizard on my laptop but received the following error message: - dataroot - Error AppNamePackage Wizard/AppName AppVersion11.0.5622/AppVersion AppInstallLocationC:\Program Files\Microsoft Office\ADE11\/AppInstallLocation AccessVersion12.0/AccessVersion AccessBuild4518/AccessBuild AppFileNameC:\Program Files\Microsoft Office\ADE11\WZADE.MDE/AppFileName IsAddInFalse/IsAddIn FileTypeMDE/FileType ModNameForm_frmWizardShell/ModName ProcNameForm_Load/ProcName ErrorNumber5/ErrorNumber DescriptionInvalid procedure call or argument/Description Time2009-08-06T11:28:20/Time /Error /dataroot Three questions: Does this mean the Developer Extensions will not work with Office 12, and that I cannot create a package on my laptop? Does this mean that if I used the Packaging Wizard on my desktop with Office 11 (also on my desktop) that the ultimate package could not be installed on a computer that had Office 12 on it? Has there been another Developer Extensions issued that I don’t know about, and if so, how do I acquire it? Thank you for any insight you can provide. It would be so nice if these could all play well together... Mary |
#3
|
|||
|
|||
Access Developer Extensions and Office 12
sweeneysmsm wrote:
Does this mean the Developer Extensions will not work with Office 12, Correct. You have to use the Dev Extensions with the version of Office/Access for which they were designed. and that I cannot create a package on my laptop? You could download the free A2007 Dev Extensions and use those instead. Does this mean that if I used the Packaging Wizard on my desktop with Office 11 (also on my desktop) that the ultimate package could not be installed on a computer that had Office 12 on it? Yes, a runtime built with one version of Access can be installed on a system with another version of Access. The problem though is that the last version of Access installed or explicitly chosen by a shortcut to the msaccess.exe gets used. So the client may have installed an A2007 MDB/MDE/ACCDEB/ACCDE but your just installed runtime version of Access 2003 tries to execute that file. And now you get blamed for their corporate system not working. Has there been another Developer Extensions issued that I don’t know about, and if so, how do I acquire it? Thank you for any insight you can provide. It would be so nice if these could all play well together... Well, the runtime versions installed play together as well as do the retail versions. However us developers understand the problems and can deal with them. Users OTOH haven't a clue. Now one alternative is to ship your app in A2000 MDE format. Albert Kallal created a sample inno script which checks to see if a version of Access is installed. If not it tells you to install a runtime version of Access. If installed then it continues to install your FE MDE and other assorted files.' http://groups.google.com/group/micro...34660872?hl=en Sample inno script which "wraps" the package wizard install into a single .exe http://groups.google.com/group/comp....191bf1f8?hl=en Deploying updates to your software in a Runtime environment for Access 2007 http://www.members.shaw.ca/AlbertKal...allExample.htm Tony -- Tony Toews, Microsoft Access MVP Tony's Main MS Access pages - http://www.granite.ab.ca/accsmstr.htm Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/ Granite Fleet Manager http://www.granitefleet.com/ |
Thread Tools | |
Display Modes | |
|
|