Importing Office 2007 Quick Access Toolbar to Office 2010

I want to bring over my QATs created in Office 2007 (running in Windows XP Pro) into Office 2010 (running in Windows 7 Pro). Because there is no way to export the Office 2007 QATs to a file, I can't do the normal importing a customization file
directly from within Office 2010. However, if I copy my word.qat (or excel.qat, powerpoint.qat, etc) file created in Office 2007 over to the appropriate folder in Office 2010, and just change the file extension from ".qat" to ".officeUI" it brings up
my QAT settings in Office 2007. It looks okay and seems to function properly like this.
I think this will work, but I'm not sure if it will cause other problems. It seems to look okay. Will I run into trouble with it later?
Sorry to bump such an old thread... but I couldn't find anything about a possible 2007 > 2013 migration. The strict change in extension names doesn't enable the old .qat file to be imported (in MSO2013 the new extension is .exportedUI) -- however,
digging into the old .qat and new .exportedUI files, it seems all I needed to do was add <mso: cmd app="Word" dt="0" /> to the start of the file and presto... imported without any problems. Let's see if it all runs fine... (and if it works in Excel
too) (phew!)

Similar Messages

Can't Open File Explorer -- How can I reset the Quick Access Toolbar from outside of File Explorer?

First of all, this is not a virus. This is my a bug within windows explorer itself.
So, I added the properties button to the QAT, and it displayed it as an expandable menu, like this: ";" but with small arrows like this: ">". didn't want this, I wanted to click on it and immediately display the properties of the file
to me. So, I hovered over it, right-clicked on "Properties" in this menu and added it to the QAT. Of course, this crashes File Explorer. Now whenever I try and open it, it crashes, so I have to assume that the corrupted button has been saved.
So, my question is: How do I reset the QAT from OUTSIDE of file explorer? Regedit magic? Any ideas?
Thanks for stopping by,
Trolleyman.
Edit: Just so you know, I can navigate through my systems files using the 7-zip file manager. Phew.

Thanks from me too, Niki. This first happened with Windows 8.0 File Manager a week ago,, and despite much research I couldn't discover the cause so eventually I resorted to restoring the system drive from backup (luckily I make daily backups,
so didn't lose much work).
Without knowing the cause a few days later I again tried to alter the Quick Access Toolbar and the problem reappeared. Should I again resort to restoring the entire system drive, the thought horrified me. But
luckily while doing a bit more research prior to resorting to the same drastic recovery, I cane across this post of yours and it worked!
It doesn't seem to be happening with Office 2007's or Wordpad's Quick Access Toolbar, so presumably it's a File Explorer bug (a.k.a. Windows Explorer in Windows 7, of course). Have Microsoft recorded this as
a bug -- if not, why not -- and when are they coming up with a fix?

Embed word document in C# winforms, Have to disable/hide Quick access toolbar.

Hi Team,
Currently i am embedding a word document in winforms. I need to disble/hide/remove the quick access toolbar from the word, i was tried in different ways like below ways in C# but it's not working .
With oDocument.Application.CommandBars("Standard")'disable the standard toolbar
.Enabled = False
.Visible = False
End With
WebBrowser1.ExecWB OLECMDID_HIDETOOLBARS, OLECMDEXECOPT_DONTPROMPTUSER'toggle between "reviewing" and "standard"
toolbar
End Sub
Any help would be highly appreciate.Thanks.

Hi Ravindra
The code you're trying to use is for the old "toolbar" GUI that was discontinued in the Office applications starting with version 2007. CommandBars is still present in the object model and does interact with the new "Ribbon" interface
to a certain extent, but it's NOT used to affect visibility.
The Ribbon GUI, introduced in Office 2007, is defined by "Ribbon XML" and cannot be affected by code running from outside the application interface, nor by code running in-process that's not part of the same "container" as defines the
Ribbon XML.
From the screen shot you provide, it looks like you want to work with a specific type of document ("Custom Letter")? If yes, then it would be best for you to create a template that contains the Ribbon definition you want to provide for that type
of document. In order to suppress the QAT you need to use the "startFromScratch" command for the customUI which also means that the Ribbon XML must define the ENTIRE Ribbon interface you want to provide to your users.
You'll find the basics about customizing the Ribbon in the three-part article "for developers". You can find links to that, as well as to other information concerning the Ribbon,here:
https://social.msdn.microsoft.com/Forums/office/en-US/ba8c9d0b-7312-4503-8167-f2ef86f17435/information-on-the-office-fluent-ui-ribbon-for-developers?forum=officegeneral
Cindy Meister, VSTO/Word MVP,
my blog

Word 2013 - Publish as PDF or XPS button causes excessive registry queries / high CPU when added to quick access toolbar

After installing Office 2013 Pro Plus on our XenApp 6.5 environment we noticed a drop in performance. Using taskmanager we could see winword.exe hit 20+% CPU usage when filling just 1 line with the same letter.
Some investigating lead us to the "Publish as PDF or XPS button", when it is added to the quick access toolbar the cpu usage doubles during keystrokes. Using procmon I noticed excessive registry reading, up to 150,000 lines in 10 seconds.
It seems to be a constant loop of the same queries to approx. 100 components in HKLM\Software\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Components\
I reproduced this in 3 different setups:
Win2008R2 + Office2013 Pro Plus 32-bit + Office 2013 updates until 12-nov 2014
Win 8.1 Laptop + Office2013 Pro Plus 32-bit + Office 2013 updates until 05-jan 2015
Win 8.1 Desktop + Office2013 Pro Plus 64-bit + Office 2013 updates until 17-dec 2014
Can anyone verify this behaviour? For now we've removed the shortcut from the quick access toolbar in our environment.
Here's a small portion of the queries.
19:22:49,7117781 WINWORD.EXE 1484 RegQueryKey HKLM SUCCESS Query: HandleTags, HandleTags: 0x0
19:22:49,7117861 WINWORD.EXE 1484 RegOpenKey HKLM\Software\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Components\1A89310DF62F54544A1465F790A7757D SUCCESS Desired Access: Read
19:22:49,7117969 WINWORD.EXE 1484 RegQueryValue HKLM\SOFTWARE\MICROSOFT\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Components\1A89310DF62F54544A1465F790A7757D\00005109110000000100000000F01FEC SUCCESS Type: REG_SZ, Length: 130, Data: C:\?Program Files\Common
Files\Microsoft Shared\OFFICE15\MSO.DLL
19:22:49,7118058 WINWORD.EXE 1484 RegCloseKey HKLM\SOFTWARE\MICROSOFT\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Components\1A89310DF62F54544A1465F790A7757D SUCCESS
19:22:49,7118154 WINWORD.EXE 1484 RegQueryKey HKLM SUCCESS Query: HandleTags, HandleTags: 0x0
19:22:49,7118232 WINWORD.EXE 1484 RegOpenKey HKLM\Software\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Components\837CF31208764B643868B58117357D20 SUCCESS Desired Access: Read
19:22:49,7118332 WINWORD.EXE 1484 RegQueryValue HKLM\SOFTWARE\MICROSOFT\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Components\837CF31208764B643868B58117357D20\00005109110000000100000000F01FEC SUCCESS Type: REG_SZ, Length: 112, Data: C:\Program Files\Microsoft
Office\Office15\OUTLFLTR.DLL
19:22:49,7118415 WINWORD.EXE 1484 RegCloseKey HKLM\SOFTWARE\MICROSOFT\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Components\837CF31208764B643868B58117357D20 SUCCESS
19:22:49,7118511 WINWORD.EXE 1484 RegQueryKey HKLM SUCCESS Query: HandleTags, HandleTags: 0x0
19:22:49,7118586 WINWORD.EXE 1484 RegOpenKey HKLM\Software\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Components\FDFFB7C3B3B7DA048B21B3A72D1BF855 SUCCESS Desired Access: Read
19:22:49,7118694 WINWORD.EXE 1484 RegQueryValue HKLM\SOFTWARE\MICROSOFT\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Components\FDFFB7C3B3B7DA048B21B3A72D1BF855\00005109110000000100000000F01FEC BUFFER OVERFLOW Length: 144
19:22:49,7118769 WINWORD.EXE 1484 RegQueryValue HKLM\SOFTWARE\MICROSOFT\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Components\FDFFB7C3B3B7DA048B21B3A72D1BF855\00005109110000000100000000F01FEC SUCCESS Type: REG_SZ, Length: 134, Data: C:\Program Files\Common
Files\Microsoft Shared\OFFICE15\FLTLDR.EXE
19:22:49,7118849 WINWORD.EXE 1484 RegCloseKey HKLM\SOFTWARE\MICROSOFT\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Components\FDFFB7C3B3B7DA048B21B3A72D1BF855 SUCCESS
19:22:49,7118949 WINWORD.EXE 1484 RegQueryKey HKLM SUCCESS Query: HandleTags, HandleTags: 0x0
19:22:49,7119023 WINWORD.EXE 1484 RegOpenKey HKLM\Software\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Components\BF574A30F66E6D54186C7F15B116E7A3 SUCCESS Desired Access: Read
19:22:49,7119123 WINWORD.EXE 1484 RegQueryValue HKLM\SOFTWARE\MICROSOFT\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Components\BF574A30F66E6D54186C7F15B116E7A3\00005109110000000100000000F01FEC SUCCESS Type: REG_SZ, Length: 100, Data: 20:\CLSID\{000C0126-0000-0000-C000-000000000046}\
19:22:49,7119203 WINWORD.EXE 1484 RegCloseKey HKLM\SOFTWARE\MICROSOFT\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Components\BF574A30F66E6D54186C7F15B116E7A3 SUCCESS
19:22:49,7119295 WINWORD.EXE 1484 RegQueryKey HKLM SUCCESS Query: HandleTags, HandleTags: 0x0
19:22:49,7119369 WINWORD.EXE 1484 RegOpenKey HKLM\Software\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Components\017CCC9DE12773C4FAD559D2951B14C6 SUCCESS Desired Access: Read
19:22:49,7119466 WINWORD.EXE 1484 RegQueryValue HKLM\SOFTWARE\MICROSOFT\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Components\017CCC9DE12773C4FAD559D2951B14C6\00005109110000000100000000F01FEC SUCCESS Type: REG_SZ, Length: 128, Data: 22:\Software\Microsoft\Office\15.0\User
Settings\Mso_Core\Count
19:22:49,7119544 WINWORD.EXE 1484 RegCloseKey HKLM\SOFTWARE\MICROSOFT\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Components\017CCC9DE12773C4FAD559D2951B14C6 SUCCESS

I'll do that, I'm however still interested if somebody can confirm the excessive registry queries.
As a brief test, I captured winword.exe (2013) registry-reads on my Win8.1 pc (64bit Windows), with ProcMon.
this is over a capture period of less than one second
2092 of 2352 contain "component" in the reg path
this is when I have winword open and whilst "File, Export" is displayed (this is what offers the export-to-PDF option)
vs. 168 registry operations in an interval of 10 seconds, by winword.exe, if word is simply "running in background with an open blank document"
I'm not sure if that is useful, but it seems an awful lot of registry reads/writes from an application which isn't apparently doing anything at the time..
EDIT: similar registry read/write rate, when save-as-pdf is added to QAT (again sitting idle on a blank document). the registry read/write rate drops back down to 160 if the save-as-pdf feature is then removed from QAT.
Don
(Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)

Access Outlook Shared/Delegated contacts in Word 2010's Quick Access Toolbar (QAT)

Hello Nerds,
Is there any way to access Outlook Shared/Delegated contacts in Word 2010's Quick Access Toolbar (QAT).
I am able to see shared/delegated contacts in Outlook by clicking "Open Shared Contacts" but Word's 2010 QAT does not have any option to add/open shared contacts.
Thanks much

Hi,
Do you mean add Delegated Access or Shared Contact command to QAT in Word 2010?
These two commands only belong to Outlook, so we can’t add them to QAT in Word 2010.
More reference about Add commands to Quick Access Toolbar:
http://office.microsoft.com/en-001/support/add-commands-to-the-quick-access-toolbar-HA102814964.aspx
Hope it can be helpful.
Regards,

Auto-Hide Ribbon - Quick Access Toolbar disappears

In Outlook 2013 I select to auto-hide the ribbon but this also hides the Quick Access Toolbar. Why does it do that. When the ribbon is hidden there is still space for the quick access tool bar so why hide it? It would be really useful to be able to see the
quick access tool bar (in the available space) when the ribbon is auto-hidden. Now, if I want to use the quick access toolbar with the ribbon hidden I have to un-hide the ribbon first.
Can we see the quick access tool bar when the ribbon is hidden?

Hi,
By default, Auto-hide Ribbon causes the tabs, ribbons and quick access toolbar to completely disappear, giving you the maximum amount of space to edit documents.
If you want to show the Quick Access Toolbar, we can just select Show Tabs which
shows only tabs, along with the quick access toolbar, but without their associated ribbon commands.
Best Regards,
Steve Fan
Forum Support
Come back and mark the replies as answers if they help and unmark them if they provide no help.
If you have any feedback on our support, please click
here

Can't import office 2010/13 files into SQL Server. I'm out of ideas!

Hi
I have SQL Server 2012 installed on my Windows 8.1 Instance. I want to be able to import and export data to Access 2013 files *accdb. I have Office 64 bit installed on my machine. I have searched a lot and can't find exactly what to do
to fix this. I have even done a clean install of SQL, but still no bananas.
I have downloaded and installed Microsoft Access Database Engine 2010 but that didn't help.
Any ideas?

OK, now I know why I have never solved this problem. When I try to install Microsoft Access
Database Engine 2010 32 bit version, I get an error saying I cannot install the 32 bit version while running Office 2013 64 bit.
I found this blog http://knowledge.autodesk.com/support/autocad-civil-3d/troubleshooting/caas/sfdcarticles/sfdcarticles/How-to-install-64-bit-Microsoft-Database-Drivers-alongside-32-bit-Microsoft-Office.html
which talks about the opposite problem, but not my problem. Does anyone know of a work around to install the 32bit version of ADE with 64 bit Office?

QUICK ACCESS TOOLBAR WONT WORK

I am not able to scroll thru the commands with FM7.2p158 in Windows 7 Pro.
You can see the button go in, it just does not make the toolbar scroll to the next line of tools? please help.
Any way to get around this? is/are there some other tool to get the same jobs done e.g. delete a line, add a line (I know some of the left click commands)
thanks,
Carl

Hey Rod, I think you misundersood. Or perhaps Lilybiri and I did.
It seems our understanding is that ZippySkippy is wanting a toolbar in the Captivate application itself. Your understanding seems to be that ZippySkippy is asking about projects you create using Captivate.
I suppose it's now in Benjamin's corner to say who correctly understood the request and who didn't. LOL
Cheers... Rick
Helpful and Handy Links
Captivate Wish Form/Bug Reporting Form
Adobe Certified Captivate Training
SorcerStone Blog
Captivate eBooks

Problem Saving Files to A Sharepoint 2010 Site from Office 2010: Saves locally by default rather than to the correct sharepoint site

Hi we are starting to use sharepoint 2010 / word 2010 and have found an interesting bug/problem. Sometimes when a user tries to save a file (by clicking on the save button in the quick access toolbar for word 2010) the save dialog comes up with the
users local "Documents" folder as the path (not the correct sharepoint path where the document should be saved). (I should say that we are creating the file from sharepoint by using a toolbar on the document library, with the new button)
We are using a content type and a template attached to the document library when we create the file.
This is really annoying because the user might not notice that the document is saving locally and not to sharepoint. I have found a strange workaround which involves clicking the [File] tab on the ribbon in word 2010, then clicking "Save and Send"
and then clicking the save button again. At this point word 2010 seems to "remember" that it is trying to save document to sharepoint and shows the sharepoint document library.
This is a real nuisance which could lead to documents being lost/misfiled if people don't realize that this is happening. Can anyone help me?
Thanks
Kevin
krd

Saving files to SharePoint Document Library.
For a test try this:
Word 2010
Disable all options in "Protected View"
(-> Word Backstage -> Options -> Trust Center -> Protected View)
Now you can create a new document in your document library. The
save dialog comes up with the correct sharepoint path.
Hope this helps
DJWGermany

Office 2010 Don't print blank lines when data fields are empty

How do you do this in office 2010? Where do we go now?
This used to be under the Tools menu in previous versions:
On the Tools menu, click Mail Merge.
In the Mail Merge Helper dialog box, click Merge.
NOTE: You must select the main document and data source for the merge before doing step 2.
In the Merge dialog box, under When Merging Records, click either:
Don't print blank lines when data fields are empty.
-or-
Print blank lines when data fields are empty.
Click Close in the Merge dialog box, and then click
Close in the Mail Merge Helper.
NOTE: If you made no changes in the Merge dialog box, the
Close button is not available. Click Cancel instead.
Back to the top

Hi,
In Word 2007 or Word 2010, you can add
Mail Merge Helper to the Quick Access bar, and perform the steps then.
To add the
Mail Merge Helper command in the Quick Access Toolbar in Word 2007, follow these steps:
a.
In Word 2007, click the
Microsoft Office Button, and then click Word Options >
Customize.
In Word 2010, click File > Options > Customize Ribbon.
b.
Click
All Commands in the Choose commands from, and then click
Mail Merger Helper in the Choose commands from list.
c.
Click
Add, and then OK.
Best Regards,
Sally Tang

Office 2010 & 2007 - Excel and Access File Locking Out On the Network With Multiple Users

This is also posted in the Office 2010 - IT Pro General Discussions, but was suggested to repost here, since a definitive answer was not found.
Hi,
An issue that's happening is that Excel and Access files are locking on the network. We're currently using Office 2007 and 2010.
Here are some different scenarios that are happening:
When opening the file it is locked out by “User X” which is the person that has the file locked out and no one else can open the file.
When opening the file it is locked out by “User Y” which is NOT the actual person, but is locked out by “User X” and no one else can access the file.
When opening the file it is locked out by “…another user” which is generic and no one else can access the file.
The two more common events are incident 1 and 2 with 3 happening the less common.
This message will continue until the sessions are closed through computer management on the file server.
The file server is running Windows Server 2003.
This does happen on both Windows XP and Windows 7 clients.
This does happen for users using Office 2007 and Office 2010.
There are two sets of Office 2010 Users when it comes to patches. Everyone has the most current patches with Office 2010 SP2 while anyone that has Microsoft Project 2010 is using all the current update before Office 2010 SP2.
All users that are using Office 2007 have all the current patches and service packs.
Another variable is that we have users that will leave a file open on the network for 3+ days and after a while it will lock the file out.
Also we have Shadow Copy that runs daily on the system which I'm not for sure if that impacts anything if a file is opening during that time.
Any ideas on how to mitigate the lock out issues would be appreciated.
Thanks,
Binary Process
Edit November 12, 2013: This issue can occur if and if not another person actually has the file open. If the person doesn't have the file open then there is a hung connection which needs to be disconnected by going to the Computer Management of the File
server.

Hi Binary,
I know that the description of the hotfix does not relate to the issue. The purpose is to install it for upgrading SMB related file.
A similar issue I encountered before:
http://social.technet.microsoft.com/Forums/windowsserver/en-US/b7fcc59b-52d9-4a02-863a-1a529bcb8cb1/temp-doc-etc-files-dont-close-after-a-file-closes-this-causes-locked-files?forum=winserverfiles
It is resolved by upgrading SMB files so maybe it will help on your case.
Another hotfix which may related:
http://support.microsoft.com/kb/983458
If you have any feedback on our support, please send to [email protected]

Safari compatibility with Microsoft Office Live Meeting 2007 Web Access

I'm trying to use Live Meeting 2007 Web Access, and the test page is saying that the software isn't supported by my platform. The troubleshooter states that system requirements are Safari 1.3 or 2.0, and my Safari is 3.2.1 Can anyone advise how to remedy this without scrapping my current version and adding the earlier one? It also says it needs Apple Java 1.4.2...I'm completely lost there. Thanks for your help!

Hi,
Did the issue happen for all Live meeting or just for one Live meeting?
If the issue happen for all Live meeting, please update OCS client and then test again.
Try to reset IE and use other media player to test the issue.
Best Regards,
Eason Huang
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Eason Huang
TechNet Community Support

Office 2010 and Office 2007 on same machine

I am currently running the following:
Xcelsius Engage 2008, service pack 4
Windows 7, 64 bit
Office 2007 Ultimate, 32 bit
Everything working well
I purchased a version of Office 2010 Home and Student - it has both 32 and 64 bit versions. My plan was to keep Excel 2007 on my machine so that Xcelsius would still work. Then, I loaded the 64 bit version of 2010. It seemed to work for a session, Xcelsius seemed to pull on the Excel 2007. Then I restarted my machine and Xcelsius could not launch excel. It seemed to occur right after I tried to import an xls that had been created in Excel 2010.
My question is: is it possible to successfully run Xcelsius with Office 2010 Home Student 64 bit? Should my strategy of keeping Excel 2007 have worked? Or should I accept 32-bit is the reality for the next few years?
Also, I see that Xcelsius does not support the Home and Student version of Office. Why is that? Isn't excel, powerpoint, word, the same regardless of the version?

Hi,
As soon as you restart your system office version is updated to latest version of office that you have installed(64 bit)
Go through the following link for supported platforms and versions :
http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/601b2c00-da68-2e10-7c81-af37a0a6d378.
Hope this link can clear all your doubts .
@Sri

Scripted Import MRU list from Office 2010.

Hello all, i was wondering if anyone could help with this, we have a script that exports the MRUs as reg keys from office 2010, it exports the following as a .reg file on the source machine, and on the destination machine it imports the reg key so a user
moving machines has all of their recent documents:
Windows Registry Editor Version 5.00
[HKEY_CURRENT_USER\Software\Microsoft\Office\14.0\Word\File MRU]
"Max Display"=dword:00000019
"Item 1"="[F00000000][T01CF9ABB0FC89840][O00000000]*C:\\Users\\USERNAME\\Documents\\FILENAME.xlsx"
This works absolutely fine when coming from 2010 and going to 2010, however since we have put 2013 on the destination machines, the script doesn't work due to the user ID field being unique to each user:
Windows Registry Editor Version 5.00
[HKEY_CURRENT_USER\Software\Microsoft\Office\15.0\Excel\User MRU\AD_CC97ADD968A5532BF33D5693E751F2355768058F0819CBCF30AD727C87634047\File MRU]
"Max Display"=dword:00000019
"Item 1"="[F00000000][T01CF9ABB0FC89840][O00000000]*C:\\Users\\USERNAME\\Documents\\FILENAME.xlsx"
would anyone know of a way to export from 2010, obtain the AD_CC9...... ID, and change the .reg file to this as part of a scripted import?
as it stands im having to open each application (word, excel, powerpoint) and click on file to generate the AD_CC..... reg key, then copy the key name from registry editor, and edit my 2010 exported .reg files to re-import manually on the destination machine.

You might want to take a look at below thread:
http://community.spiceworks.com/topic/461503-office-2013-and-recents-list
http://social.technet.microsoft.com/Forums/en-US/07267496-cfcd-4cf0-810a-8ee91b213dfc/office-2007-to-2010-migrating-file-mru-not-working?forum=officesetupdeployprevious
For a specific script, I would suggest you to seek assistance in Microsoft OneScript center, that's the dedicated place for script issues:
http://social.technet.microsoft.com/Forums/scriptcenter/en-US/home?forum=ITCG
Thanks,

LabView database connectivity toolkit 1.0.1 compatibility with MS-ACCESS 2010 / Labview report generation toolkit for Office 1.1.3 compatibility with Office 2010

In the very near future we will be forced to upgrade to Office 2010 Company wide and I am a little concerned with some of our older test platforms that have applications built in LabView 8.2.1. These applications save data to MS-ACCESS 2000 databases using the LabView database connectivity toolkit 1.0.1. Office 2003 is also loaded on these test platforms with all test reports generated using the LabView report generation toolkit for Office 1.1.3.
I have not gotten my hands on a copy of Office 2010 yet to see if there will be any compatibility issues. Does anyone have any experience in this area?

The MS-Access part is fairly well isolated through the ADO interface LabVIEW uses. The only possible problems there IMHO are difficulties with possible Acess compatibilities itself such as an example, SQL statement you may have invoked directly through the ADO interface. Maybe you did use a depreciated command back then that has since been removed. As long as the only thing you do are simple INSERT and SELECT statements only, I would expect it to just keep working.
The Report Generation interface is a different beast. Microsoft manages to change the Automation interface with every version of office in a way that strongly binding applications like LabVIEW break on. There is no good way around that except not changing those methods, but that is a cause that has been lost already. You will certainly have to verify the version dependant Report Generation API VIs to still work with Office 2010 and most likely you will have to make some changes to those VIs to make them work again with the modified ActiveX interface of Office 2010. Note, that I have no experience with porting report generation to Office 2010 but I have had some headaches from porting that between Office 97, 2000, 2003, and 2007.
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

Importing Office 2007 Quick Access Toolbar to Office 2010

Similar Messages

Maybe you are looking for