LiveCycle designer 8.2 issues with Office 2010

Good Day All;
We are in the middle of upgrading from Windows XP / Office 2003 to Windows 7 (32bit) / Office 2010 and I was wondering if there are any issues with Livecycle designed and Office 2010.
I have been that Adobe Acrobat 8.2 does not support Office 2010. I ran into that with trying to install PDF maker.
Any comments will be helpful.
Regards
Chomp

We recently upgraded to Win 7 and to Acrobat 9 (didn't upgrade Office so cannot comment on that). The only issue I have found (and I can only assume it was
due to the OS upgrade or the Acrobat upgrade (or both)) is that I lost use of my Preview tab. In order to be able to preview a form now in LiveCycle, I must first open an instance of Acrobat, otherwise I don't even get a Preview tab. Also, the preview doesn't show up in the Preview tab...it actually opens in Acrobat.
Weird, but I'm getting used to it.
Jo

Similar Messages

  • Issues with Office 2010 and Acrobat Pro 8

    Good Day All;
    We are in the middle of upgrading from Windows XP to Windows 7 with Office 2010 and I was wondering if there are any issues with importing Office documents into Acrobat Pro 8. I have found out that there are a couple of issue with Office 201 and LifeCycle Designer.
    Any comments would be helpful
    Regards
    Chomp

    Acrobat 8 is not compatible with Microsoft Office 2010 and the PDFMaker plugins will not install. Only Acrobat X is compatible with Office 2010, and at this time only in 32-bit mode.
    Acrobat 8 is also not officially compatible with Windows 7, again Acrobat X is the first version to carry approval for that OS. It will still install, but Adobe cannot guarantee it will operate perfectly in all cases, and doesn't provide install support for that combination.

  • Offline Activation issues with Office 2010 Professional Plus

    I have a volume license for 17 seats for MS Office 2010 Professional Plus, along with a MSDN license which authorizes us to have 50 seats.
    I have activated the software offlline via the telephone.  After about six months the licenses go inactive and requires me to reactivate the product again.  This has happened serveral times. 
    The network consisting of three servers: One Domain Controller, two member servers one of which has Exchange 2010 and the other is the endpoint management secrutiy server.  There are 17 clients with windows 7.  The network does
    not connect to the web.
    I have been on the phone with support but the level of the help desk has not been very informative.  In the 90 minutes that I was on the phone, I was directed to go to various websites, i.e. volume licensing ...  these sites were not
    helpful. Toward the end of the phone support I was finally transferred to a U.S. representative.  This individual stated that I would need to have a support contract in place prior to recieving help for a product that should install and be activated without
    an issue.
    I do not have a KMS, I'm completely isolated from the Internet and would like some direction on this matter.
    /r
    Mitch Page
    ISSM
    CISSP

    Hi, this is a public/community forum, not an official support channel, but we can try to help you.
    VL editions of Office can be activated by either KMS product key (the default pre-embedded key) or by MAK product key.
    KMS doesn't require any kind of web connection at any time (you could activate your KMS host by telephone activation. Your KMS clients then contact your KMShost only, via your internal network. No internet connection is needed)
    Or, you can use MAK. MAK requires you to "install" your CSVLK product key in each computer (overwriting the pre-embedded KMSclient pkey) and then activate each computer. You can activate MAK installations via internet or telephone.
    Typically, once an MAK pkey is activated, it remains activated, unless the computer is subjected to "hardware changes" or some form of data restore or recovery.
    Although you don't have KMS implemented, you do seem to have enough computers (the minimum is 5) to consider KMS.
    6 months is an interesting milestone. 180 days is exactly the timeframe for a KMSclient to become unlicensed if it been unable to contact a KMShost.
    Perhaps you could check the current licensing configuration/status on a couple of computers, to confirm their current situation?
    - on a computer, open an elevated (run as admin) CMD console
    - execute: cd \Program Files (x86)\Microsoft Office\Office14
    (or on a 32bit OS, execute: cd \Program Files\Microsoft Office\Office14
    - execute: cscript ospp.vbs /dstatusall > c:\osppOUT.txt
    This will produce the text file, showing all *possible* Office licenses, and the currently installed one should show as "Licensed".
    You can post the results back here for us to review for you. (there is only a partial pkey displayed, so nothing sensitive will be revealed)
    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!)

  • Does Visio 2013 work with Office 2010?

    Does Visio 2013 work with Office 2010?

    Tuesday 01/06/2015
    Take a look at this Microsoft KB
    KB2784668
    It has one reference to Visio and the support / install order of Office.
    Now with that said, regardless of 2010 vs. 2013, you can NOT mix 32-bit or 64-bit versions of Office.
    For example, lets say I installed Office 2010 SP2 64-bit
    (FYI... How to determine Office 2010 SP file version
    KB2121559)
    I then want to install Visio 2013 32-bit, the install will not work.
    You cant mix 32-bit and 64-bit versions of Office Products.
    TechNet article explains more...TechNet
    (FYI...A few more people are asking the same question...)
    Forum 1
    Forum 2
    (How to determine which version 32-bit or 64-bit version of Office is installed 
    Stackoverflow.com)
    Above article is dependent on Full Office being installed...  You can also query the DisplayName REG_SZ key as well, it will report back the Office version.
    Registry Location:
    HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall
    Look for the Office GUID in my example for 2010 64-bit SP2....
    Now with the above said, below are notes from one of our desktop support techs in regards to issues we have seen internally running Office 2010 32-bit SP1 and SP2 on Win 7 x64 Enterprise with Visio 2013.....
    Office interops. The ability for office and other applications to communicate with other office apps.
    The first instance today: User sends corporate communications from word using the send to mail recipient feature. After visio 2013 installed, he received a message stating that word could not communicate with outlook, to either repair office or check the
    server. Office was repaired, new outlook profile created. After research, discovered the office is sensitive to various versions in regards to interops. Discovered that Visio 2013 was installed around the time user experienced issues. After uninstalling visio,
    when launching word it began to configure (like for a first time install), the send mail to recipient feature began working. This probably will affect anyone with visio 2013. Visio 2010 was not reinstalled afterwards, as user barely uses it and was hesitant.
    Installation files are still on his machine in the event that he does need it reinstalled. Office version is 14.0.7109.5000 User is on Office 2010 SP2
    The second instance today: Teammate stopped working 3 weeks ago according to user. After working through several support groups here and working with the vendor support, the vendor noted that some dll’s from the application were not registered. If that didn’t
    fix it they suggested a reimage. After registering the dll’s, issue persisted. After further troubleshooting, determine that the feature that did not work for user consisted of teammate downloading information from a system, parsing it, then outputting it
    to a word document. The application provided no error of any sort, it just would never get to the word document portion. Discovered that Visio 2013 was installed around the time that the issue occurred, and that the issue appeared to be related to office interops.
    I uninstalled Visio 2013 and it began working as designed. In both cases Visio 2013 had been installed on 11/25/2014 (I didn’t see any corporate communication about an upgrade, but maybe one took place?). Office version is 14.0.7109.5000 User is on Office
    2010 SP2
    I’m not sure if you have much experience with interops, but pretty much anytime you want to communicate with a different office application, that is how it is done. Per my reading through various Microsoft KB’s and support forums, different version interops
    do not play well together always. It appears that these applications are trying to communicate to office 2010 (v 14) using 2013 (v15) interops, only after installing visio 2013 professional. Users were both Windows 7 x64. We also had a group of several users
    who also ran into issues with sharepoint not working in any browser, turned out the problem was Visio 2013 was well....
    Feel free to research more, but my own research comes down with having both 2010 and 2013 interops on the machine. To simplify it, the applications and office apps are being told to communicate using office 2013, and but only listen in 2010, causing problems.
    Its not causing problems with every simple interop, or we would see it far more widespread, but we are going to continue to see the “ghost” issues where Visio 2013 is the root cause, but nothing is really going to scream it.

  • Problem opening documents from SharePoint (2013) libraries with Office 2010 and 2013 components installed

    Hi
    I've been encountering the problem of Office files failing to open from SharePoint 2013 libraries with the prefix of 'ms-excel:ofv|u|' etc. in the url. Following the
    helpful questions and answers in the forum, I've identified the likely cause as the fact that my main Office installation is 2010, but I also have installed OneDrive for Business 2013 (which I need in order to sync document libraries with my local drive).
    The solution I've seen suggested elsewhere of deactivating the SharePoint integration of Office 2013 components fails for two reasons: there is no way (or at least, I can't find one) of deactivating SharePoint integration probably because, deactivating
    SharePoint integration would likely stop the syncing of libraries/folders.
    One thing that I have noticed in my case that I've not seen mentioned elsewhere is that if I right-click a document and select 'open in new tab/window' the required
    document opens directly in the relevant office package. I don't know if this is a useful observation, but it seems to be new information.
    My question is, is there a way I can continue to sync libraries and open Office documents directly in Office 2010? My thoughts are possible changes to registry settings
    (which I can do, but don't know enough to find the correct ones myself) or (re)installation of software in some appropriate order to leave the correct settings.
    I have 'repaired' my Office 2010 installation without any observed affect on behavior.
    Thanks
    Ray
    (I've just seen a suggestion that Office 2010 SP2 may fix this issue. I've requested to test this, but whilst this may fix my problem, rolling it out to
    other users may be more problematic. In the meantime, other suggestions of solutions are welcome)

    Hi,
    According to your description, it is a good way to do a test about office 2010 SP2, here is an article about this issue- limitations of using the OneDrive for Business sync app with Office 2010 applications , it may help you.
    http://office.microsoft.com/en-us/sharepoint-help/solve-problems-youre-having-with-the-onedrive-for-business-sync-app-HA104047973.aspx
    Paul Shui
    Microsoft Online Community Support
    Please remember to click “Mark as Answer?on the post that helps you, and to click “Unmark as Answer?if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread

  • Lync 2013 OCT deployment on machines with Office 2010. Installation Failure

    Hi,
    In our environment, we have Win7, Office 2010 x86. (no plans to upgrade all of Office to 2013 as yet)
    I'm trying to deploy Lync 2013 x86, and have packaged an MSP using "setup /admin" for later deployment via SCCM.
    Now I know there are no problems running Lync 2013 with Office 2010 as it works fine if you manually install.
    Strange thing is, when I try running the setup with MSP for silent install, it runs silent and all looks well although all the Office Tools shortcuts are created and there are files under the Program Files folders for Office\15.0 as expected
    but not Lync itself. ie: no lync.exe file or shortcuts.
    Reviewing the setup log doesn't show any obvious errors that I can tell.
    Also after this, if I go through the "Add/Remove Components" under Uninstall Programs\Lync 2013, and I can see in there that it DOES already show Lync as being installed, if I just click continue, it runs through the setup process and
    then Lync will be installed
    I've also tried this same process using the Full "Office Pro Plus 2013" and only select Lync to install and the same thing happens.
    Has anyone else come across this issue or could point me in the right direction.
    For the OCT (setup.exe /admin) the only settings I've changed from defaults are:
    - Filled in the Organisation name
    - Set KMS licensing, display level to none and suppress modal
    - some regkeys for some default settings for GalDownloadInitialDelay, ShownFirstRunOptin
    - Force on Lync (Run from My Computer)
    I'm running "setup.exe /adminfile Lync_x86.MSP" in my case to test this MSP.

    I had the same issue. As soon as I updated to the latest Admin admx/opal files, it worked great.
    Cheers,
    JeffCSP
    This issue was introduced when SP1 was released, and is detailed here:
    http://blogs.technet.com/b/odsupport/archive/2014/03/21/lync-2013-and-onedrive-for-business-are-not-installed-when-installing-office-2013-with-service-pack-1.aspx
    (it remains uncorrected by MSFT :(
    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!)

  • Outlook 2013 Not Responding and Offline Address Book Issues with Office 365

    Around 3 months ago I setup a small business with Office 365 for email. They have 10 PCs, all running newly installed Windows 7 Professional 64-bit, eight with Office 2013 and two with Office 2010. All are connected to a local domain (Server Essentials
    2012) with a single internet connection through a new TP-LINK router. Each user logs into their own PC only.
    The network runs perfectly, internet connection is good but there seems to be RANDOM, INTERMITTENT issues with email not being SENT from Outlook every so often. Email will sit in the outbox for up to an hour sometimes before, eventually, being sent. Incoming
    email seems ok, although this is more difficult to tell. At others times, email will be sent instantly - the size of the message and any attachments makes no difference.
    The issue has happened at some point on every one of the PCs but no particular PC/user seems worse than any other. When email is stuck on one user's PC it can still be sent ok by other users at the same time - so the internet connection is not down. Users can
    can always login to the OWA service ok and iPhones etc. all sync ok even when email is stuck in the Outbox.
    To debug the issue I have worked on one particular user's PC and carried out the following changes - 
    Changes that made no difference
    I have checked the router. A SPI firewall is available on the router but this is switched off.
    I have changed the MTU on the router with no effect.
    There are no unsual add-ins to Outlook
    Outgoing email virus scanning is disabled
    Outlook is NOT integrated with Lync
    The OST file is around 1.7 GBytes is size.
    I have recreated the Outlook profile twice but this made no difference
    Switched OFF "Cached Exchange Mode" - this made things worse !
    The Outlook address book is set to \Offline Global Address List
    I have disabled with Windows firewall on the client PC - no change
    I have adjusted the KeepAliveTime for packets in the registry of the PC to 20 minutes
    Changes that reduced the frequency of "Not Responding"
    I have changed the Outlook automatic Send/Receive time from 30 to 10 minutes - this seemed to help 
    Possible Related Problem
    I have attempted to download the offline address book manually - this hangs at "Copying offline address book template file" in the Send/Receive dialog and there a NO OAB files in the data file location on the PC. 
    So the only measure that has so far "helped" has been the Outlook Send/Receive time change - now set to 10 minutes. Even so, Outlook will occasionally go "Not Responding" for 30 minutes or more (no windows active - only option
    is to close and reopen Outlook).
    There does seem to be a problem with the Offline Address book. I can download this ok for this user on my home PC (Outlook 2010) but this will not download manually on the work pc with Outlook 2013 (despite following all the debug steps above).
    On work PC I can see literally hundreds of "Schannel" errors in the Windows System event logs - 
    Error - Event 36888 Schannel
    The following fatal error was generated :10
    The internal error state is 10
    These errors occur every 2-4 minutes continually all the time Outlook is running. When Outlook is closed the "Schannel" errors stop !
    Can anyone suggest what else to try, please ?
    I have already investigated this issue on the Office 365 Community Forum, and the Outlook forum and they suggested that it was a client (i.e Outlook) issue and that I should post here for further information.
    Thanks for reading !

    An update to this problem.
    I brought one of the office PCs back to my home network and connected it up there. With no changes to the PC I was immediately able to download the Offline Address Book without errors.
    This suggests to me that there must be some problem with the internet connection or router setup in the office environment.
    The router is a TP-LINK W8970. The internet connection is PPPoA. I have seen some suggestion that an SPI firewall can cause issues. This router has an SPI firewall but this feature is disabled on the router.
    While investigating this issue I have frequently been connected remotely to an office PC - sometimes for up to an hour or more. During these periods I have not experienced any connection dropouts so the actual internet connection seems to be ok (i.e. it is
    not dropping out). 
    However, something seems to be preventing the Outlook client from connecting properly with the Office 365 Exchange server in the office environment - or something is dropping the connection to Outlook. Does anyone know of any router settings that might affect
    this ?
    I could try changing the office router but I do not have a spare available. Can anyone suggest a reasonably low cost, currenbtly available router that they know definitely works in the Office 365 environment so that I could buy this for test purposes ?

  • Unable to print multiple copies of documents on Win7 machine with Office 2010

    Since upgrading to Windows 7, I have been unable to print multiple copies of documents in any MS Office 2007, 2010, Word Pad or Adobe Reader 9.  I also experience the same problem if I print from Word Pad.  The issue appears to be associated with the Collate Option in the Print Dialog box.  If the Collate box is checked, I only get one copy of the document.  If I uncheck the Collate box I get as many copies as I choose.   The problem is that with the Collate box unchecked, I have to collate multiple copies by hand, and with 10 – 20 copies of multi-page documents that can be quite a chore.
    The ironic thing is that MS Visio 2003, on the same machine, prints and collates as many copies as I choose, with the Collate box checked.   
    I can print multiple copies of Word 2003 documents from my wife’s Win XP machine to the same printer, but not from my Win 7 machine with Office 2010.
    My printer is an HP LaserJet 1320nw and I have downloaded and installed the latest printer drivers from the HP Web site.
    Has anyone experienced this problem, and if so, are you aware of a solution other than unchecking the Collate box?

    I have the same issues with my LJ1320. I have Office 2010 and Windows 7 Ultimate 64 bit.   However, my printing problem is more widespread since I have been unsuccessful at printing multiple copies of all types of documents, not just from  Office 2010.  For example, I have the same problem trying to print multiple copies from  Internet Explorer.
    I also have other problems printing  from Office 2010 that you may not have discovered yet.  I cannot print Excel spreadsheet grid lines from Office 2010 if those documents were originally created in an earlier version of Office.  I tried saving them as Office 2010 documents and also using compatibility mode but nothing worked.  These same documents print fine on the same printer from my laptop which uses Windows Vista and Office 2007.  Also Excel spreadsheets originated in Office 2010 print nicely.
    Looks like HP has a few bugs in their printer drivers.
    I note that HP released a new Universal Print Driver for Windows PCL5x64 on Feb 18, 2011 (Version 5.2.6).  Have you tried it yet? 

  • 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

  • Project Professional 2013 Installations Fails with Office 2010 installed on Windows 7 x86

    When attempting to install Project Professional 2013 Pro (x86) on Windows Professional x86 PC that has Office 2010 ProSp2 installed client getting an error message at the end of the installation "Project 2013 has encountered an error during setup".
    I have gotten the installer to work on x64 PC with Office 2010 installed. (Something worth noting that even thought I set the reboot to prompt its automatically reboots without warning but, appears to be working.)  I also tried using the OTC, custom XML
    file and just running setup.exe and get the error no matter what. When looking in the logs I there are MSI installer error with an error: Product:
    Microsoft Project Professional 2013 - Update '{A6FFA77F-C1C1-43D3-A2C7-6A5B68138D9F}' could not be installed. Error code 1603. Windows Installer can create logs to help troubleshoot issues with installing software packages. Use the following link for
    instructions on turning on logging support: http://go.microsoft.com/fwlink/?LinkId=23127
    Without having to uninstall Office 2010 what do I need to modify in the installer to get it to Project 2013 Pro to install on the x86 machine?
    Thanks

    Hi,
    Your environment will support 32 bit of Project professional 2013 (x86) as you have Windows and Office of (X86).
    You try to modify registry then you wont face issue.
     The issue when you hit a "1653" is that Windows
    Installer "DisableRollback" is set. Office 2013 requires that "rollback" be enabled. If you are getting a "1653"
    error in your logs as Ken did then the solution is to delete the "DisableRollback" (or set to '0') at the following registry keys:
    HKEY_CURRENT_USER\Software\Policies\Microsoft\Windows\Installer
    HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\Installer
     these are the issues I've seen:
    Scheduler service was stopped. At a cmd window typing "net start schedule" resolves the problem.
    CMD.exe was customized via the following registry key. Solution was to temporarily disable the customization by changing autorun value to autorun_old. 
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Command Processor
    HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Command Processor
    Permission issues - seems some custom permissions affected Ingram's install which he explained in his previous post.
    Environment variable "ComSpec" had been modified (semicolon added). Fix was to remove the added semicolon (there should be no semicolon).
    The way to identify you are hitting this specific issue is if in the %temp%\OfficeSetup.log there is a mention of "Office64MUI.msi" failing to install with return value of 1603
    If you want to enable verbose logging via the following key, rerun your failed install, and collect all the setup and MSI* logs that will give more information.
    [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Installer]
    "logging"= "voicewarmup"
    kirtesh

  • Cannot Sync With Office 2010

    Office 2010 has been released to Technet, schools, and other organizations. Maybe RIM should think about pulling one of their dusty programmers out of the closet to write a snippet of code so we can actually sync with Office 2010? I really getting sick of lookinbg at the "no message store" errors. Makes me want to buy a *real* smartphone.

    ddvogt wrote:
    Message to Blackberry:
    I hope you listen..
    The issue may be that Nokia bought the third party company that was doing the synch under Blackberry.
    Blackberry: You need to fix that problem or switch to another third party. You may otherwise see a vast exodus to Android based phone.
    I hope you have not come to be too big to care about your customers.
    Hello again!
    It seems you are posting this same information all over our forums. We welcome your input, but it's not really necessary to say the same thing over and over. Trust us...they get it. It is simply impossible for them to release any forward looking information -- things such as "2010 compatibility will be available on (insert date here)" are strictly forbidden as per the TOS of this site.
    In regards to your hope that RIM will see your message -- these forums are a user-to-user support channel, not a user-to-RIM conduit. As such, it is unlikely that they will see what you have written. However, if you have specific and constructive ideas for them, I have heard that they accept such via email to [email protected]
    Good luck!
    Occam's Razor nearly always applies when troubleshooting technology issues!
    If anyone has been helpful to you, please show your appreciation by clicking the button inside of their post. Please click here and read, along with the threads to which it links, for helpful information to guide you as you proceed. I always recommend that you treat your BlackBerry like any other computing device, including using a regular backup schedule...click here for an article with instructions.
    Join our BBM Channels
    BSCF General Channel
    PIN: C0001B7B4   Display/Scan Bar Code
    Knowledge Base Updates
    PIN: C0005A9AA   Display/Scan Bar Code

  • Help with OBDC connection in Windows 7 64bit with Office 2010 32 bit.

    Hi,
    Many moons ago I wrote an application in Java that configured XP machines after they were sysprep’d and deployed. I am currently migrating all our workstations to Windows 7, and was checking my application still worked and queries the correct registry keys etc.
    As it turns out however I don't even get going as I believe the application is unable to connect to the ODBC Microsoft Access Driver in Windows 7 64bit with Office 2010 32 bit. Below is the code I have always used and no longer works. I am hopeful that someone can tell me how to modify the command to work on Windows 7 64bit. If I browse to C:\Windows\SysWow64\OBDCad32.exe all the drivers I need are there I think, but if I open OBDC from Administrative Tools the Drivers tab is empty but for SQL. Anyway I will shut up and below is the code I used to use:
         public IOMakeConnection()
         dm = new DisplayMessage();
         ioed = new IOEncryptDecrypt();
         url = "jdbc:odbc:DRIVER=Microsoft Access Driver (*.mdb);DBQ=" + getPath() + "Config.mdb;Uid=admin;Pwd=password";
              try
              Class.forName("sun.jdbc.odbc.JdbcOdbcDriver");
              connection = DriverManager.getConnection( url );
              catch( Exception e )
              system.out.println( "" + e );
              errorObtainingPath();
    The exception is always thrown as my little app that requests the database path always loads.
    Thanks in advance,
    Cheers Kris

    Hello again,
    Sorry for the delayed response, I have been out of the office for a few days.
    I have solved the issue, and as stated above the issue was the way I was launching the application. Below is a summary of the issue and the resolution.
    My problem was that in Windows 64bit if you click on ODBC in Administrative Tools the Drivers Tab only includes an SQL Driver, and my code reference a Microsoft Access Driver to query the database. That said however if you browse to C:\Windows\SysWow64 and open obdcab32.exe it opens the 32bit version of ODBC, and the Microsoft Access Driver (*.mdb) is listed.
    Basically what I need to do therefore is get my code to access the “32bit” version of ODBC in a Windows 7 64bit environment, so my application was able to read the necessary information from the Access Database associated with it.
    I understand that this is not a coding issue directly, but assuming people still use Java to open an Access Database on a Windows 7 64bit OS, this may be of help.
    So previously I ran the following command, from the “Target” box in a shortcut to execute the java code:
    cmd.exe /C SET CLASSPATH=C:\SCAConfigurationUtility && CD\SCAConfigurationUtility && JAVAW SCAConfigurationUtility
    Windows 7 64bit, defaults to the 64bit version of Java, and just seems to plain fail if you only have the 32bit version installed. To overcome this I forced the java executable that I was using to be the 32bit version, and used the system switches available in Java 7 (-cp does not appear to be available in Java 6)
    So my Shortcut now has this in the “Target” box:
    java.exe -d32 -cp C:\SCAConfigurationUtility SCAConfigurationUtility
    And this in the “Start in” box:
    "C:\Program Files (x86)\Java\jre7\bin"
    Or by using the target below the same shortcut works in XP
    "C:\Program Files\Java\jre7\bin"
    Thanks for all the help,
    Regards Kris.

  • Error installing BI Publisher Desktop in Windows 7 64bits with Office 2010

    Hello
    I'm having a problem when trying to install the latest version of BI Publisher Desktop on my computer (Windows 7-64bits with Office 2010).
    Almost at the end of the installation it appears a message box saying "Template Builder installer failed: Cannot run installer while Mocrosoft Word is running". Now, i made sure all Office apps are closed, as well as IE windows. What i've noticed is that right before this error appears, a process for WINWORD.exe is open - by the installer.
    How can i fix this?
    Many thanks for your replies

    I've tried runnig the installer with Windows XP SP3 compatibility and it worked.

  • Adobe Acrobat 8 Standard compatibility issues with Office 2007 and Windows 7

    I just updated my platform to Windows 7 and upgraded from Microsoft Office 2003 to Microsoft Office 2007.  The PDF printer did not download and realized that there are compatibility issues with Office 2007.  How could I get this fixed?

    Buy Acrobat 11.

  • Acrobat PDFmaker 9 won't work with Office 2010

    Acrobat is Adobe's powerful and long-running pdf handler.  It's good software, but according to Adobe tech support in India, has known incompatibilities with Office 2010.  We can't create pdf files from any Office document or spreadsheet.  Adobe dropped the ball on this one, Office 2010 was out in beta for long enough for big developers like Adobe to get with the program.  Avoid Acrobat 9 until Adobe fixes it.

    I see a lot of people commenting that they had Adobe Acrobat 8.xx Pro and it worked fine with Microsoft Office 2010.
    That was not my experience.
    I downloaded MS Office 2010 and had the latest update of Adobe 8 Professional. (Don't know which release that was, but I keep my Adobe programs automatically updated.) As soon as I tried to use Adobe Acrobat to combine Excel files into a PDF, the PDFMaker functionality failed. This is why I purchased Adobe Acrobat 9, because my previous version did not work with MS Office 2010.
    It was incredibly infuriating to find out that upgrading did not resolve my problem, nor would going back to the previous install of Acrobat 8 Pro work for me. So, Adobe cheated me out of $160 for no reason, and after spending 6+ hours uninstalling, reinstalling and all kinds of other nonsense, I still can't use my PDFMaker plugin.
    The same thing happened with Adobe 8 and Microsoft Office 2007. The first version of Adobe 8 wasn't compatible, but then Adobe released a patch for Acrobat 8 that made it work with 2007. FOR FREE. I would say that we, the customers, have a reasonable expectation that the same should be done for Adobe 9, also at no extra charge.
    There is no way in hell that I'm buying Adobe Acrobat 10. Adobe has been incredibly dishonest about this problem and they're not getting one more red cent of my money. I'd rather scan my documents to PDF or use the Distiller.
    I'm quite sure I'm not alone in this sentiment, either.

Maybe you are looking for