已鎖定 Access 2013/Access 15

  • Friday, July 06, 2012 1:46 PM
     
     

    Dear Office enthusiasts:  Is anyone but me kinda scared about the lack of information coming out on the new Access 2013/15??Has anyone heard anything positive?  like, better SQL integration, UI improvements, new controls, new sharepoint web access features?

    Is MS finally going to kill my favorite application????  Help!!!

    -PrimeTime21


All Replies

  • Wednesday, July 11, 2012 9:26 PM
     
     
    I like Access, but Microsoft is going to kill my favorite application.
  • Tuesday, July 17, 2012 1:34 AM
     
     

    I tried to open an Access database project .adp file and it says it is no longer supported. I need this to be able to support more than 256 fields per table. I am very dissapointed in this latest version. No improvements for business.

  • Tuesday, July 17, 2012 2:31 AM
     
     

    I just learned there is no DBF import/export support. So that will suck for me, as we deal with DBF files everyday, for varies customers and internal applications.

    Not sure why MS thinks not supporting DBF files is good. That is really bad on MS part. Without DBF Import/Export all of our automated program and process will cease to function. Of course we cannot simply keep using our previous versions for ever, our only hope is that MS will add that feature back in, or an alternative office suite supports what we need.

    Why MS? Why would you take away DBF files?

    Glenn P. Bowlsby

  • Tuesday, July 17, 2012 3:37 PM
     
     Answered

    Hi @Primetime21,

    There are a bunch of new things in Access 2013 that we will covering on the blog over the next few weeks at http://blogs.office.com/b/microsoft-access/

  • Tuesday, July 17, 2012 3:37 PM
     
     

    @taohhhhghh

    No way! Expect a bunch of updates on http://blogs.office.com/b/microsoft-access/ in the next few weeks :)

  • Tuesday, July 17, 2012 3:39 PM
     
     

    @Steve Sanford

    ADP's are no longer supported in Access 2013, we will have a longer more detailed post about this issue on the blog during the preview at http://blogs.office.com/b/microsoft-access/


  • Tuesday, July 17, 2012 3:40 PM
     
     

    @Broggy69

    DBF Import/Export is no longer supported in Excel & Access 2013. We will have a longer more detailed post about this issue on the blog during the preview at http://blogs.office.com/b/microsoft-access/

  • Tuesday, July 17, 2012 3:56 PM
     
     

    How about a nice summary, one paragraph per item, of all the new stuff in Access 2013?

    so far all I have found is the What's New topic (have to search for it) in the built in HELP (look for the very small "?" at the upper right.  I read it and was underwhelmed.

    Hopefully MS can get out some information sooner than "the next few weeks".

    bob


    Bob Alston

  • Tuesday, July 17, 2012 4:01 PM
     
     

    Hi Bob,

    We will have a blog post with an overview of all the new stuff shortly.

  • Tuesday, July 17, 2012 10:39 PM
     
     

    Will there be any native support for SQL Server in Access 2013 that gives similar functionality to Access data projects? (Otherwise why would Microsoft want to remove functionalty that supports the use of other Microsoft Products?)

    Will Access 2013 be able to use more than 255 fields in a table?

  • Wednesday, July 18, 2012 2:10 AM
     
     Answered

    More information about Access 2013 is here. and check out What's new

  • Friday, July 20, 2012 5:21 PM
     
     

    Column Limit is literally reason #1 I moved to Access Data Projects 12 years ago.

  • Tuesday, July 31, 2012 1:41 AM
     
     
    Well I guess from the responses we have seen so far Microsoft IS going to kill my favorite application. If you need any decent fuctionality with regards to supporting for more than 255 fields, SQL views and the type of fucntionality supported with adp files, Access 2007 is the best version yet!
  • Thursday, August 02, 2012 12:53 PM
     
     

    I don't understand Microsoft's philosophy with Access. it WAS the greatest RAD program to date. It seems like Rotten Apple is going to take over that with FileMaker.

    I wouldn't mind paying more for Access for all it does! Along with enhancing it, maybe with some LightSwitch features. Why kill a good thing???

    Scratching my head...Primetime21

  • Tuesday, August 21, 2012 9:49 PM
     
     

    it doesn't matter how much details are given as to why DBF supported is gone. Not only do we receive DBF files from customers, but we use a program called Business Objects Postal Soft, and we use DBF files as the incoming and outgoing for the file. We use Access to automatically Import and Export the DBF files during the various task, and have a VB module made with Access 95 and has been upgraded all the way through Access 2010.

    So without DBF support we will have to create a whole to program from scratch to find a better solution. MS really messed up on this one. DBF support has to stay. It is needed and required, and probably will be until a faster file format is created. 

    Text files doesn't work for what we do. We have tried time and time again. DBase II or DBASE IV works best for what we do.

  • Tuesday, September 18, 2012 10:21 AM
     
     

    Office 2013:

    New skin, totally deprecated, DBF ADP (Project), MS SQL incompatibility with aggregated NUMERIC / DECIMAL fields... They are killing their own product...

    I believe they're trying to push something else... but this something else its unusable, its not 1/10 of Access 2000 for example was...

    I still have hope they wake up... Restore the functions and increase MS SQL compatibility.

    Office 2000 still the best Office Ever. Fast, reliable, MSSQL fully compatible. 2002-2013 only skin changes and deprecation thru the years...

    Please Microsoft, WAKE UP...

  • Friday, October 26, 2012 9:40 PM
     
     Proposed Answer Has Code

    In this article it is described that you can add Xbase (dBASE) support:

    msdn.microsoft.com/en-us/library/office/ff845606(v=office.15).aspx

    If have an accdb database with linked dBase (.dbf) files which work perfect in Access 2010 after upgrade to Access 2013 that database did not work anymore.

    After adding the required registry entries it now works.
    Please note that the required acexbe.dll is in the /OFFICE14 folder, NOT in the OFFICE15 folder where the new engine driver are located.

    The required registry entries are (exported it form my working situation):

    Windows Registry Editor Version 5.00
    
    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\15.0\Access Connectivity Engine]
    
    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\15.0\Access Connectivity Engine\Engines\Xbase]
    "win32"="C:\\PROGRA~1\\COMMON~1\\MICROS~1\\\\OFFICE14\\Acexbe.dll"
    "NetworkAccess"=hex:01
    
    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\15.0\Access Connectivity Engine\ISAM Formats]
    
    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\15.0\Access Connectivity Engine\ISAM Formats\dBASE III]
    "Engine"="Xbase"
    "ExportFilter"="dBase III (*.dbf)"
    "ImportFilter"="dBASE III (*.dbf)"
    "CanLink"=hex:01
    "OneTablePerFile"=hex:01
    "IsamType"=dword:00000000
    "IndexDialog"=hex:01
    "IndexFilter"="dBASE Index (*.ndx)"
    "CreateDBOnExport"=hex:00
    "ResultTextImport"="Import data from the external file into the current database. Changing data in the current database will not change data in the external file."
    "ResultTextLink"="Create a table in the current database that is linked to the external file. Changing data in the current database will change data in the external file."
    "ResultTextExport"="Export data from the current database into a dBASE III file. This process will overwrite the data if exported to an existing file."
    "SupportsLongNames"=hex:00
    
    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\15.0\Access Connectivity Engine\ISAM Formats\dBASE IV]
    "Engine"="Xbase"
    "ExportFilter"="dBase IV (*.dbf)"
    "ImportFilter"="dBASE IV (*.dbf)"
    "CanLink"=hex:01
    "OneTablePerFile"=hex:01
    "IsamType"=dword:00000000
    "IndexDialog"=hex:01
    "IndexFilter"="dBASE Index (*.ndx, *.mdx)"
    "CreateDBOnExport"=hex:00
    "ResultTextImport"="Import data from the external file into the current database. Changing data in the current database will not change data in the external file."
    "ResultTextLink"="Create a table in the current database that is linked to the external file. Changing data in the current database will change data in the external file."
    "ResultTextExport"="Export data from the current database into a dBASE III file. This process will overwrite the data if exported to an existing file."
    "SupportsLongNames"=hex:00
    
    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\15.0\Access Connectivity Engine\ISAM Formats\dBASE 5.0]
    "Engine"="Xbase"
    "ExportFilter"="dBase 5 (*.dbf)"
    "ImportFilter"="dBASE 5 (*.dbf)"
    "CanLink"=hex:01
    "OneTablePerFile"=hex:01
    "IsamType"=dword:00000000
    "IndexDialog"=hex:01
    "IndexFilter"="dBASE Index (*.ndx, *.mdx)"
    "CreateDBOnExport"=hex:00
    "ResultTextImport"="Import data from the external file into the current database. Changing data in the current database will not change data in the external file."
    "ResultTextLink"="Create a table in the current database that is linked to the external file. Changing data in the current database will change data in the external file."
    "ResultTextExport"="Export data from the current database into a dBASE III file. This process will overwrite the data if exported to an existing file."
    "SupportsLongNames"=hex:00
    

    • Proposed As Answer by i4jordan Friday, October 26, 2012 9:41 PM
    •  
  • Wednesday, November 28, 2012 1:09 PM
     
     
    We get DBF files daily that we have to parse into SQL using access dlls. We just finished upgrading all the computers to Win 8 and Office 2013. Now we have to downgrade. Did Microsoft not learn a long time ago that new products must support existing business?
  • Saturday, December 01, 2012 3:51 PM
     
     

    @i4jordan

    Do you have any idea where to get the Acexbe.dll file?  I looked in my common files folder and can't find it.  The one mistake I think I made was removing the Office 2010, through contorl panel, from my machine.  I must have deleted that file when that was done.  Now I am looking for a new way to put this file on my computer.

    I am going to attempt to look in my Office 2010 CD to see if I can find it, but I have a funny feeling I am going to have to uninstall Office 2013, reinstall Office 2010, and then reinstall Ofice 2013 (or just stay at 2010).

    Thanks

    Alan


    • Edited by Alan Beebe Saturday, December 01, 2012 3:51 PM
    •  
  • Saturday, December 01, 2012 4:03 PM
     
     

    Why not?  This looks to be a big discussion among a few people, yet it doesn't look to be answered or even discussed.  I am also working with a legacy system that has a need to link to 2-3 different dBase files and now I can't.  I have never heard of a program removing legacy access.  If that has happened, and there is no hope of it being brought back, then how about a step-by-step explanation on how we can do it?  I wouldn't mind using anotehr tool, or process, but this made Access so simple to connect to other database formats, and now that functionality is lost.

    I have also looked at the blog, and it is good if you are looking for new features, but nothign about taking care of people hwo have used it for years and require a legacy suport system.  I guess MS' thinking is to scrap everything you have ever done and start from scratch.  Wake up and move into the real world, business leaders do not want to rewrtie their programs every time there is an update.

    Thanks

    Alan

  • Tuesday, December 04, 2012 11:25 PM
     
     

    I just learned there is no DBF import/export support. So that will suck for me, as we deal with DBF files everyday, for varies customers and internal applications.

    Not sure why MS thinks not supporting DBF files is good. That is really bad on MS part. Without DBF Import/Export all of our automated program and process will cease to function. Of course we cannot simply keep using our previous versions for ever, our only hope is that MS will add that feature back in, or an alternative office suite supports what we need.

    Why MS? Why would you take away DBF files?

    Glenn P. Bowlsby


    ME TOO!!!!
  • Tuesday, December 04, 2012 11:28 PM
     
     
    AGREE!
  • Tuesday, December 04, 2012 11:47 PM
     
     
    Did you find it?
  • Tuesday, December 04, 2012 11:53 PM
     
     

    Perfect! I am now able to import my DBF files. Thank you!!!!

    Ron

  • Thursday, December 13, 2012 3:34 PM
     
     
    So do we just edit the registry and that's all?
  • Friday, December 28, 2012 2:55 PM
     
     
    No, I tried to download it from another web site, but was not able to.  I am still unable to import or link a dbase file.
  • Tuesday, January 08, 2013 10:09 PM
     
     

    i4jordan what steps did you take to get the dbase support. Just editing the registry? Can you provide step by step instructions on what you did?

    Thank you in advance.